Viktor Holmgren

Hi @Tarnadas, I generated a new tag/release v5.0.0. Will try to generate a new API key :)

Have been really busy but now have tried this on OSX as well. Here we run in to the exact same issue. This very aggressive cleaning (i.e only keeping latest...

After a little more research into the output directories of Cargo. Only the `incremental` folder can cleanly be removed in its entirety without affecting the build at all. Both `deps`...

I hope to manage to allocate some time to work on a nightly-only implementation using `build-plan` during the holidays and see what I can come up with. Would be nice...

I think the best approach is the one suggested in #5 instead, i.e do two separate steps in which one outputs a timestamp file before the build step, and then...

Yes, that is true. I am not familiar with the build-plan so I am not sure if it may fail due to nightly compiler not being compatible with some dependency...

Ah ok. As long as build-plan is only useable for unstable I will be very unlikely to implement it as the primary/only solution although I agree it is probably the...

Yes, I will keep this issue open until the build-plan is stabilized

Adding a file.timestamp file would work very well, since currently sweep can only look at access times as an approximate measure. That said, I do not see any use for...

Currently you will have to use the stamp and file loading features outlined in the README. I.e cargo sweep -s then cargo build, cargo test etc and finally cargo sweep...