Morgan :)

> Note that there is already an optimization in place that files with _no_ annotations will be skipped without resolving them. > > It is possible this just needs to...

> The scaling issue could be solved by offering a "reportUsed" instead of "reportUnused". So instead of thousands of unused assets, we have a couple dozens of used ones. >...

> > Hmm, are you sure? I guess that would involve using the parsed AST before the element model, but I couldn't find something like that, if you meant in...

> ^ Couldn't there be an official way to hook to this optimisation? > > I often subclass Generator myself to have more freedom over how I generate code. So...

> And a big part of the challenge is long term support. Dart changes really fast. It's already hard to keep up with Analyzer changes as a code generator author....

I'm thinking of build_runner blocking accidental use of `dart:io` at some point, which would mean it needs to be in `build_runner`. Other than that though, yes, it's very lint-like.

I would expect to have a smooth path whereby we first warn on `dart:io` use and give people a way to say "this is intentional" to get rid of the...

Thanks Rexios! I'd exactly like to identify cases where builders are using `dart:io` and figure out whether there is a different way or whether we should have a note "you...

One complication, `GeneratorForAnnotation` just passes through `T` to `TypeChecker.fromRuntime`. So we can't do an equivalent check: we need to add either a way to pass a name or to pass...

> One complication, `GeneratorForAnnotation` just passes through `T` to `TypeChecker.fromRuntime`. So we can't do an equivalent check: we need to add either a way to pass a name or to...