So I wondered if we could somehow automatically find incremental ices using the spaceheater approach (throwing cpu at the problem).
So far I have been iterating through all commits of a repo and building them one by one, but we can also use clippy to modify the sources!
So I came up with this command chain:
cargo build ; cargo clippy --all-targets --fix -Zunstable-options --allow-dirty -- --cap-lints warn -Wclippy::pedantic ; cargo build
We first build the crate, then apply clippy lint suggestions and build again to see if the incremental verification catches anything. :)
I believe there was a program to automatically run incr comp through all commits in a project. It was used when incr comp was still unstable.
I think that was https://github.com/michaelwoerister/cargo-incremental
Yeah, https://github.com/nikomatsakis/cargo-incremental was what we actually used. It required a lot of maintenance because not every commit would build.
startup idea: a globally-accessible database recording whether given commits are expected or unexpect to build. (potential features include: recording how may of each; what hosts (i.e. os+cpu) worked or didn’t; recording uploaded diffs against commits to “fix” them) ...
many some search tools would benefit from knowing such info ahead of time.)
(further next steps beyond that: make a proof-of-work currency based on the results, called “buildcoin”)
((Last part is a joke: I know part of proof-of-work is ability to verify result, which is not tenable here))
Last updated: Oct 21 2021 at 21:46 UTC