[zigzag312]

Sounds like performance is the biggest issue. I'm guessing the macros need to run after every keystroke. That creates big time constraint that while nice it's not really needed.

Due to AOT compilation, some form of (pre)compile time code generation is needed, but it doesn't need to be macros. It doesn't need to be instantaneous, but it also shouldn't take minutes.

Adding features directly into the language removes the need for some code generation.

Augmentations will already make code generation much nicer to use.

build_runner needs to become more integrated so that IDEs would read build_runner's config and run it automatically.

[krzat]

IMO it would make the most sense if code generation was integral part of the dart build system. Few years ago I described shortcomings of build_runner on github https://github.com/flutter/flutter/issues/63323, not much changed afaik.

[cjrome]

That's what you really believe huh?