3 ms·
> The eventual removal part doesn't tend to happen. For Rust it can't happen, because of the backwards compatibility guarantees: you can mark an API as depreca
by estebank 3y ago
> The eventual removal part doesn't tend to happen.
For Rust it can't happen, because of the backwards compatibility guarantees: you can mark an API as deprecated, and potentially make those unavailable in later editions, but code that compiled on 1.0 (2015 edition) should continue to compile in perpetuity, so the API has to stay around in the stdlib so that older code still works (we dont have an stdlib per edition, it wasn't even originally envisioned to have editions affect the stdlib, only syntax and semantics). It shouldn't be a problem, but it is an inconvenient burden.