---- Mark H Weaver <m...@netris.org> wrote: > There's another option: we could properly track the compile-time > dependencies of each module, and automatically consider a .go file stale > if _any_ of its compile-time dependencies are newer than it. > > To be more specific: I think we need to record, in every syntax > transformer bound at top-level, the name of the module where it's bound. > Then, within the dynamic extent of `compile-file', (probably using a > fluid) we'd need to accumulate the set of modules whose macro > transformers are used during compilation of the file. This set of > modules (the compile-time dependencies) would be included in the .go > file.
I think we should have this. -Dale
