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
Very productive meeting with @benlesh and lots of great feedback.
Handling via .then/.catch/.finally - do we need synchronous way to handle these too?
Examples for a consumer initiating early termination (emitter.resolve(), emitter.reject())
Useful to pre-emptively cover what-if scenarios e.g. tearing down an Emitter generating infinite values
There were footguns with operators on prototype, essentially global mutable state. Functional approach is much better, not just stylistic.
Eager vs lazy example
Subscription/unsubscription is bidrectional in Observables, but values always flow down.
Observable-Promise integration via promise-returning forEach was more of a concession, still requires subscription.
Iterator design has weird edge cases, e.g. what does .return with a value actually do, handling that can be esoteric, or what does tuple with value and done: true mean, etc. We should document clearly all these interactions (from and reduce take generators/iterators and have some API docs, may benefit from separate docs).
Changing shape to be closer to Observable would benefit from users already using that. We'll investigate after June trying to express both as the other to see if we can make adoption smoother.
The text was updated successfully, but these errors were encountered:
Very productive meeting with @benlesh and lots of great feedback.
.then
/.catch
/.finally
- do we need synchronous way to handle these too?emitter.resolve()
,emitter.reject()
)forEach
was more of a concession, still requires subscription..return
with a value actually do, handling that can be esoteric, or what does tuple with value anddone: true
mean, etc. We should document clearly all these interactions (from
andreduce
take generators/iterators and have some API docs, may benefit from separate docs).The text was updated successfully, but these errors were encountered: