-
Notifications
You must be signed in to change notification settings - Fork 13.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove rustc_encodable_decodable feature #134272
Remove rustc_encodable_decodable feature #134272
Conversation
r? @ibraheemdev rustbot has assigned @ibraheemdev. Use |
2993504
to
3ce5d1d
Compare
…_decodable, r=<try> make rustc_encodable_decodable feature properly unstable This has been shown in future-compat reports since Rust 1.79 (rust-lang#116016). Let's see if crater still finds any issues. Cc `@rust-lang/libs-api`
This comment has been minimized.
This comment has been minimized.
3ce5d1d
to
88960fd
Compare
@bors try |
…_decodable, r=<try> make rustc_encodable_decodable feature properly unstable This has been shown in future-compat reports since Rust 1.79 (rust-lang#116016). Let's see if crater still finds any issues. Cc `@rust-lang/libs-api`
☀️ 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
|
The built-in derives are being [removed], but crater showed problems with crates depending on `num v0.1`, where this feature is enabled by default. With this PR, we detect the missing built-ins and disable the derives, adding a build-script warning about it. Cargo won't show such warnings by default from non-path dependencies, unless the build fails. [removed]: rust-lang/rust#134272
The built-in derives are being [removed], but crater showed problems with crates depending on `num v0.1`, where this feature is enabled by default. With this PR, we detect the missing built-ins and disable the derives, adding a build-script warning about it. Cargo won't show such warnings by default from non-path dependencies, unless the build fails. [removed]: rust-lang/rust#134272
The built-in derives are being [removed], but crater showed problems with crates depending on `num v0.1`, where this feature is enabled by default. With this PR, we detect the missing built-ins and disable the derives, adding a build-script warning about it. Cargo won't show such warnings by default from non-path dependencies, unless the build fails. [removed]: rust-lang/rust#134272
The built-in derives are being [removed], but crater showed problems with crates depending on `num v0.1`, where this feature is enabled by default. With this PR, we detect the missing built-ins and disable the derives, adding a build-script warning about it. Cargo won't show such warnings by default from non-path dependencies, unless the build fails. For `num` itself, this mostly just amounts to a dependency bump. [removed]: rust-lang/rust#134272
Test build
|
Awesome, thanks a lot :) |
r? oli-obk @bors r+ |
…le_decodable, r=oli-obk Remove rustc_encodable_decodable feature This has been shown in future-compat reports since Rust 1.79 (rust-lang#116016), released June 2024. Let's see if crater still finds any issues. Part of rust-lang#134301. Cc `@rust-lang/libs-api`
…iaskrgr Rollup of 7 pull requests Successful merges: - rust-lang#134272 (Remove rustc_encodable_decodable feature) - rust-lang#136283 (Update encode_utf16 to mention it is native endian) - rust-lang#136394 (Clean up MonoItem::instantiation_mode) - rust-lang#136402 (diagnostics: fix borrowck suggestions for if/while let conditionals) - rust-lang#136415 (Highlight clarifying information in "expected/found" error) - rust-lang#136422 (Convert two `rustc_middle::lint` functions to `Span` methods.) - rust-lang#136434 (rustc_allowed_through_unstable_modules: require deprecation message) r? `@ghost` `@rustbot` modify labels: rollup
Rollup merge of rust-lang#134272 - RalfJung:destabilize-rustc_encodable_decodable, r=oli-obk Remove rustc_encodable_decodable feature This has been shown in future-compat reports since Rust 1.79 (rust-lang#116016), released June 2024. Let's see if crater still finds any issues. Part of rust-lang#134301. Cc ``@rust-lang/libs-api``
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