Remove rustc_encodable_decodable feature#134272
Conversation
|
r? @ibraheemdev rustbot has assigned @ibraheemdev. Use |
2993504 to
3ce5d1d
Compare
This comment has been minimized.
This comment has been minimized.
3ce5d1d to
88960fd
Compare
|
@bors try |
|
☀️ Try build successful - checks-actions |
|
@craterbot check |
|
👌 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
88960fd to
e9804a3
Compare
|
I don't think there really was a plan — soft destabilizing it was the extent to which it was discussed afaik. |
|
There's some mixed messaging here: the ACP says "full destabilization is not proposed due to breakage of existing code", but the lint that is emitted when using these types says this "will become a hard error in a future release". |
|
Ha, that's 100% on me. It must have been discussed on Zulip, as I wasn't aware soft destabilization was a thing before that. Anyways, it doesn't much matter. |
|
Well, seems like nobody complained about the future compat "this will become a hard error" warning that we have emitted for more than half a year now (and that is shown even when this occurs just in a dependency), so let's just see what crater says. |
|
🚧 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
|
🎉 Experiment
|
|
r? oli-obk @bors r+ |
This has been shown in future-compat reports since Rust 1.79 (#116016), released June 2024. Let's see if crater still finds any issues.
Part of #134301.
Cc @rust-lang/libs-api