set up CI

[Eh2406]

I would like to make sure that all the code compiles and that the portion of tests that can be run quickly pass. Testing crates.io takes 5cpu days, fuzzes will run as long as you let them, so cannot be run on CI merge.

[mpizenberg]

Would it be hard to randomly select a subset of roughly 1K versions on each run? I guess there would need to be a fast index to look at.

[Eh2406]

I got annoyed with waiting to scan the index on every build. So it now does the analysis based on pre-computed files on disk. And there is a command line argument to generate the files from the index. This makes local development a lot faster. And the files are (just barely) small enough to commit. So retrieving versions to test is no longer a CI blocker.

Figuring out sampling strategies seems reasonable. A subset of inputs, or a subset of tests. For example almost all of the runtime is spent on intersections, so testing only contains and complement in CI might be fast enough.

Similarly we spent a lot of time testing if versions like 0.1.0 match >5.0.0, we could use bounding_range to skip over versions that have no chance of being relevant.