Morgan :)

@jakemac53 That's fair :) I'm short on time before the weekend starts here, let me summarize quickly and I can do further writeup as needed on Monday. Summary added to...

Thanks Konstantin, very useful to see timing detail :) The concern about having to parse twice is the sort of thing I was thinking about when I filed [quantify the...

Yes, that issue uses "merge" in a more general sense, merging macro results into a single library is _part_ of the whole "merge macro output into the host model". UX...

Thanks Jake. @rrousselGit yes, in theory the "rounds" approach allows creating classes based on fields, generally it's "anything goes and reanalyze". Which is why work is needed to determine the...

I [updated](https://github.com/dart-lang/language/pull/3861) the [exploratory code](https://github.com/dart-lang/language/tree/main/working/macros/dart_model#dart_model-exploration) to talk explicitly about rounds; each macro gets one query result and can send one batch of augmentations per round, they're then written to disk,...

One thought, the amount of time needed per round is critical, and it relates to "reanalysis time". It is possible that the phase limitations are exactly, or close to, what...

Yeah, could be there's no benefit: this is tagged for the "breaking changes" milestone to mean "either do it as part of that or decide that we won't do it".

Thanks Brian. The details aren't finalized yet as to whether there will be any new files, or just pack everything into existing `pubspec.yaml` and `package_config.json`. Either way, yes, there are...

@jonasfj and I chatted about this one. Jonas has an old proposal for adding a key+value config to pubspec.yaml+package_config.json that seems like a surprisingly good fit. Jonas, could you please...

Yeah if there is additional cost just from the code being in augmentations, and additional cost related to merging macro output augmentations to a single file, this is something we...