Clarification on the Use Case for `Subscribable` in Effect Typescript
From the parameters, I thought that
However looking at the Subscribable implementation, it is just building a plain object with those two fields (get and changes) available and nothing more? What is the exact use case then? I don't get it
Subscribable was accepting an effect to generate it's value, and a stream of changes to know when to refresh itself. Kind of like a Resource that is refreshed with a stream rather than a schedule.However looking at the Subscribable implementation, it is just building a plain object with those two fields (get and changes) available and nothing more? What is the exact use case then? I don't get it
