Morgan :)

Re: reading the generated code; I agree it's rare to want to read it. It's still _important_, and so augmentations are important, because: - the _tools_ want to read it:...

> I suspect that most code generators will move to a model where they generate one file per part file, not one part file per library. In that model, this...

Thanks Bob. Edit: I think a lot of what is below is wrong, will add another post trying again :) As promised I considered what the "declarations must be before"...

Okay, thinking about this a bit more :) I think I was misled by the fact that I'm used to thinking of codegen as subclassing. I think in most cases...

Thanks @bivens-dev ... what would core language support for RFC8949 look like? I mean, compared to just doing it with codegen. Technical suggestions for specific things we could do/support are...

Re: "tooling improvements", I plan on working on build_runner performance: https://github.com/dart-lang/build/issues/3800

It looks like there is almost no problem with breakage in practice: we enforce annotate_overrides in google3, and I see exactly one(!) use of "ignore: annotate_overrides"; it's for a new...

Possibly nothing, but a thought: is `@override` actually what people want? Implementation inheritance is hard, interface inheritance is much simpler. I've always felt `@override` is overdoing things a bit by...

@Levi-Lesches `@mustCallSuper` is indeed related, thanks. Two differences: the change I suggested would be on always, rather than triggered by `@mustCallSuper`; and there would be a way to explicitly say...

@simolus3 Re: adding more information about what was read. Reads are recorded in `build_runner_core/lib/src/generate/input_tracker.dart` then exposed to tests via `build_test/lib/src/in_memory_reader_writer.dart`. Currently `InputTracker` does not know the primary input of its...