4 ms·
> Something that would be neat to see from Rust here would be a way to measure the impact of these sorts of compiler and dependency bumps in order to reduce the
by bbatha 2y ago
> Something that would be neat to see from Rust here would be a way to measure the impact of these sorts of compiler and dependency bumps in order to reduce the blast radius of this sort of thing. Ideally being able to say "this change requires X devs to do process which cost Y minutes, so it's worth investing Z minutes to avoid / document it". I often want to make public API changes to a library I maintain, but the best tool I have for understanding who those changes will affect is often a GitHub search for code.
They have such a tool, its called crater. It was used used in making the decision to delay merging the new trait impl until the new version of time was published and in wide use.
https://rustc-dev-guide.rust-lang.org/tests/crater.html https://rustc-dev-guide.rust-lang.org/tests/crater.html
- shepmaster 2y ago>> I often want to make public API changes to a library I maintain > They have such a tool, its called crater There are tools out in the wild that help crate authors do similar things. For example, I wrote my own[0] to evaluate some breaking changes for SNAFU. There's also crater-at-home[1] which I don't have any direct experience with. [0]: https://github.com/shepmaster/mini-crater https://github.com/shepmaster/mini-crater [1]: https://github.com/saethlin/crater-at-home https://github.com/saethlin/crater-at-home