Compile times

[Hixie]

Right now this approach adds dozens of seconds to the compile times even for trivial examples.

We can barely afford dozens of milliseconds, let alone dozens of seconds. Hot reload needs to remain sub-second, initial run is already too slow compared to what we'd like, tests take much too long to start (~5s compared to ~500ms back when Flutter was using Dart 1.0), and profile and release builds take a very long time (not as critical as the others but we're also at a very high time now compared to what would be pleasant for people doing performance work on profile builds).

I'm not sure what this means for this approach in general.

[jakemac53]

I would not focus on the compile times here, it is not meant to be representative of that at all. This is using a vastly different implementation than what we would actually be landing.

The final feature would be directly built into the compiler/analyzer, and not build_runner based like this is.

[jakemac53]

Fwiw the primary goal of this prototype is just to allow us to get a feel for the apis available and whether or not they provide enough expressiveness to actually solve all the problems we want people to be able to solve.