Take your favorite event emitter. What happens when you subscribe or unsubscribe while it’s already notifying the listeners? Are you sure?
Btw, does `Context.Consumer` not have similar problems? I feel like it's similar, in that it is subscribed to some `value`, and it can be added or removed from the component hierarchy dynamically. Is what you're saying, that this problem is often not solved but is solved here?
-
-
Context doesn’t use subscriptions at all so there’s no concept of change notification there.
-
Interesting. But renders are caused when the underlying values change. ...I would like to understand how it works?
- 3 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.