You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
;) When will we see some reference counting for subscribe/unsubcribe, or is this project just languishing under a full-time employed closed source owner??
So here's how I understand the degree to which we could take this:
Interface which caches (r)atoms bound to refs.
Interface to track "disposal" of subscriptions, and kill atom cache when 0 users
Some kind of sugar to use (1) and (2) with lifecycle hooks in Reagent components
Reuse existing (r)atoms that include given ref (ie. users andusers/0) via lens/cursor into the larger one.
Prune "nested" subscriptions when "parent" subscriptions are added.
Prune "parent" subscriptions when only lense subscriptions remain (ie. if watching users, then watching users/0), and reinstate the nested subscriptions.
Sounds like you just want (1)-(3)?
Not sure if (5) and (6) are even good ideas (can construct cases where they hurt more than help).
;) When will we see some reference counting for subscribe/unsubcribe, or is this project just languishing under a full-time employed closed source owner??
I want to do this in Reagent:
Thinking just going to fork and rewrite in Scala.
Jesus, Chris. Get on it. 👍 🎱
The text was updated successfully, but these errors were encountered: