Post #2227710
2025-11-19 16:42 UTC
@Mara@hachyderm.io This could totally be done if done very slowly IMO.
eg: Start by adding a feature that makes deprecation warnings show only once for an entire class of function per codebase, have that turned off by default, allow it to be disabled per-crate in Cargo.toml.
Turn it on in nightlies for a bit, wait a few months. Patches should start to flow into upstream crates to fix those warnings.
Wait for the top N% of crates on crates.io to be fixed, roll it out to beta and then stable.
Plan on doing this over 2-3 years.
Replies (1)
-
@mmastrac@hachyderm.io 2025-11-19 16:45
@Mara@hachyderm.io (this is me speaking both as a crate author and consumer - I don't think it would be too onerous at all)