Morgan :)

It means that the analyzer tracks what were the inputs to each analysis result, so it only needs to recompute when an input changed instead of when any transitive dependency...

> At the least, it should allow using the analyzer 9.0.0, which is currently not allowed. Good point, thanks, I'll take a look https://github.com/dart-lang/build/issues/4286

> > * Builders _do_ see the partial state of the part file as it accumulates source. > > Will we need new ordering guarantees or will we track multiple...

It's actually not possible to do using accumulating writes; this is the most complex part of `build_runner`, I will see if I can at least explain it without adding unnecessary...

> Yup, this is more complicated than I initially thought. I guess the best we can do here is try to optimize globbing or narrow its scope to gain at...

> also I'm not really familiar with optional builders, is there an actual package that uses it? what's a real life use-case for an optional builder? Yeah, they're a bit...

The `_benchmark` folder has some code to create test apps of various shapes/sizes using `built_value`, `json_serializable` or `freezed`. It can certainly be expanded to cover more ground. But, what I...

Benchmarking is always hard for this reason :) The most important benchmark is reasonably easy to get: do an initial build, make a small modification, do another build. By the...

Update from discussion for drift: let's have a folder with examples of community builders instead, and a test that checks that they build. This can also be a useful resource...

`build_runner` should not be compiled into your app--it is not a runtime dependency. It should work to move `build_runner` and anything related from `dependencies` to `dev_dependencies`.