-
Notifications
You must be signed in to change notification settings - Fork 3
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
🚨 [experiment] check signals v1 #114
base: master
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for g-next ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
duration phase estimated regression +9347ms [9293ms to 9402ms] OR +308.57% [306.79% to 310.39%] [14:33:19] Generating Benchmark Reports [started]
JSON: /home/runner/work/glimmer-next/glimmer-next/tracerbench-results/compare.json PDF: /home/runner/work/glimmer-next/glimmer-next/tracerbench-results/artifact-1.pdf HTML: /home/runner/work/glimmer-next/glimmer-next/tracerbench-results/artifact-1.html |
// "data" cell, it's value can be updated, and it's used to create derived cells | ||
export class Cell<T extends unknown = unknown> { | ||
_value!: T; | ||
_value!: Signal.State<T>; | ||
declare toHTML: () => string; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
YAAAS
Checking drop-in reactivity pipeline replacement with signals polyfill