proposal-emitter
proposal-emitter copied to clipboard
tc39
`reduce` is the operator that is responsible for serialising new collections, and there's a shorthand generalisation that makes it more ergonomic i.e. `reduce([])` to collect into an array, `reduce({})` to...
stage 1 requires the repo live in the tc39 org, please follow [these instructions](https://github.com/tc39/proposals#onboarding-existing-proposals) to transfer it.
Very productive meeting with @domenic and lots of great feedback. * [ ] First-class integration with Promises from ground up seems promising vs tacking some promise-returning functions, especially in overcoming...
Emitter moved to Stage 1 at the June meeting 🎉. There was also lots of productive conversations, support and ideas I want to explore before thinking about Stage 2: *...
Consider the following: ```js function on(et, name) { return { et, name }; } function map({ et, name }, fn) { const newET = new EventTarget(); et.addEventListener(name, e => {...
In particular, the `tap()` function/method should be added to `Array` before it is added to new places. I made the same point on https://github.com/tc39/proposal-iterator-helpers/issues/13.
A lot of examples seem to use functions like limit, createServer, debounce, or until. It is unclear which of these are part of the proposal. Examples that use things that...
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...
Very productive meeting with @bterlson and lots of great feedback. * [ ] Good foundation to build on, sorely need something like this * [ ] Would like to ensure...
Very productive meeting with @annevk and lots of great feedback. * [ ] Differences with Observables and better model for events * [ ] Events are not just values, they're...