This repository has been archived by the owner on Sep 16, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 232
Support using resolved ASTs for code generation #48
Comments
matanlurey
changed the title
Meta issue: Support using resolved ASTs for code generation
Support using resolved ASTs for code generation
Aug 18, 2016
This was referenced Aug 19, 2016
Tomucha
added a commit
to fnx-io/fnx_ui
that referenced
this issue
Sep 20, 2016
This was referenced Oct 27, 2016
This is now planned for the 4.0 release. |
Success. This has landed internally. I'll close this issue once there is a way to run externally. |
matanlurey
pushed a commit
that referenced
this issue
May 12, 2017
This will allow external developers to experiment with the solution to #48 ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=155672118
matanlurey
pushed a commit
that referenced
this issue
May 12, 2017
This will allow external developers to experiment with the solution to #48 ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=155672118
Done. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Lots of optimizations to the compiler, better static error checking, and further feature enhancement to Angular Dart will require that we use fully resolved ASTs, not just the raw ASTs, for code generation.
Considering this is a blocking issue to many of the issues logged today.
The text was updated successfully, but these errors were encountered: