Compile UI as code features away before constant evaluation #36910
Labels
area-front-end
Use area-front-end for front end / CFE / kernel format related issues.
front-end-fasta
P1
A high priority bug; for example, a single project is unusable or has many test failures
type-task
A well-defined stand-alone task
Milestone
Currently during constant evaluation we eliminate UI as code features (spreads and control-flow in collections) by compiling them into simpler constructs. The original syntax is a Fasta-internal implementation detail that is not part of the Kernel language. That is, the AST nodes are not in package:kernel and the Kernel transformation APIs (e.g., the Visitor and Transformer classes) do not know about them. Furthermore, this syntax is impossible to serialize and deserialize.
For the Flutter Widget inspector, we would like to perform a transformation before constant evaluation and that requires compiling these features away first so the Kernel transformation APIs work. (See #36640.)
For separate compilation, we would like to serialize constant initializer expressions in outlines, without performing constant evaluation and that requires compiling these features away first so that serialization works. (See #36635.)
The text was updated successfully, but these errors were encountered: