generated from tc39/template-for-proposals
-
Notifications
You must be signed in to change notification settings - Fork 59
Issues: tc39/proposal-signals
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Add
Signal.Buffer
alongside Signal.State
and Signal.Computed
#243
opened Oct 26, 2024 by
dead-claudia
Add batching and batched effects to solve the interoperability / multi-actor problem with batches
#239
opened Sep 6, 2024 by
justinfagnani
Clarification request: (Semantic) equivalence of push-only and push/pull models
#233
opened Jul 17, 2024 by
dehmer
Refactor Signal Class Hierarchy for Improved Type Safety and Extensibility
#230
opened Jun 18, 2024 by
DeepDoge
How to allow
set
in a Computed
to trigger a recomputation synchronously (until the result is stable)
#226
opened Jun 7, 2024 by
divdavem
Do the benefits of signals as a language feature outweigh the costs of solidification into a standard?
#220
opened May 12, 2024 by
devmachiine
Exceptions in
watched
callback leave Watcher
in inconsistent state
#209
opened Apr 29, 2024 by
prophile
"Signal.subtle.Watcher.prototype.watch(...signals)" phase 4 is vague
#205
opened Apr 29, 2024 by
prophile
Previous Next
ProTip!
Add no:assignee to see everything that’s not assigned.