Morgan :)

Yes, reporting errors for missing declarations is something most generators have to do today, and there are cases where macros have to do it too, or want to do it....

@rrousselGit That's right, definitions but not declarations; not for the sake of simplifying the feature, but for the sake of a v1 we can launch sooner :) ... with v2...

@rrousselGit @scheglov Although we have end to end code working for phase 1+2, there are some large unanswered questions; @tatumizer mentions one of them with macro ordering; macro metadata is...

@rrousselGit augmentation libraries are not ready to ship, either :) The challenge with augmentation libraries is that it's not really an independent feature, it's 95% motivated by macros. But with...

I filed https://github.com/dart-lang/language/issues/3884 with some ideas re: macros seeing the output of other macros--maybe a better default would be that they don't interact. @scheglov I hope we can get to...

@tatumizer that's exactly how `@AutoValue` works, and it's very widely used. So it's a workable model--even if people will always complain about the boilerplate, the fact that the boilerplate is...

@tatumizer you have good questions ... I have good answers, since I built exactly this, for Dart and Java, and it works well :) When I say "exactly this" ......

Yes, there is some hand waving around private declarations ;) ... it's not clear to me that letting macros see private declarations from other macros is a _feature_, exactly: we...

The downside is that it would break the JSON macro--at least I don't immediately see a nice way to keep it working. We could do a not-nice way like the...

Hmmm we could continue to publish on pub for macros / experiments. But breaking the dep from the analyzer for now would be a big help. So: analyzer -> copy...