-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Update Glimmer VM #16268
Update Glimmer VM #16268
Conversation
@@ -0,0 +1,3 @@ | |||
{ |
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.
is this not the default?
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.
I believe that file is generated automatically by VS Code and should have not been committed & merged.
4ae20a2
to
714bf1c
Compare
e2a6dd5
to
43f28a1
Compare
43f28a1
to
174b27e
Compare
Wanted to run a benchmark on this sense to get the tests passing I needed to bump the Testem timeout. TL;DR: Not stat-sig
|
@@ -82,9 +82,9 @@ export function setupEngineRegistry(registry: Registry) { | |||
|
|||
registry.register('service:-glimmer-environment', Environment); | |||
|
|||
registry.register(P`template-options:main`, TemplateOptions); | |||
registry.register(P`template-compiler:main`, TemplateCompiler); |
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.
@krisselden I ran the bench again with the Still no stat-sig.
|
if you have it handy, I would run with the runtimeStats |
This is the preemptive PR to integrate breaking changes from. glimmerjs/glimmer-vm#784