Evan Martin
Evan Martin
Thanks, opened https://github.com/evmar/n2/issues/83 about this one.
(And now fixed, maybe.)
Digging into the LLVM build, it appears check-lld is tagged into the `console` pool.
Huh, it's surprising we no longer see the performance difference from that previous change. Two guesses: - maybe lto helped? - what size is your `build1/.n2_db` file? maybe it's too...
Looking through the bincode docs, it's a little disappointing that even it uses big sizes like u64 for lengths, but it probably doesn't matter too much, and maybe using their...
If you build the `check-llvm` target in LLVM, it builds a lot more files than clang-format. I think you can interrupt the build at any point (via ctl-C) and the...
Based on this branch I created a PR that has just the serde parts without the refactoring: https://github.com/evmar/n2/pull/64/files Some random thoughts: - I don't love how this adds random copies...
(I wrote a much longer post with some thoughts about -Werror here https://neugierig.org/software/blog/2022/01/rethinking-errors.html )
It just occurred to me that a reasonable place to put configuration like this is in the ninja file itself, given that the generator is the tool where you know...
How is the external file generated? We did some experimentation around this in Ninja but in my recollection we never found a heuristic that reliably improved things. For example maybe...