-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Deprecate RustcEncodable and RustcDecodable. #83160
Deprecate RustcEncodable and RustcDecodable. #83160
Conversation
r? @kennytm (rust-highfive has picked a reviewer for you, use r? to override) |
I suppose this technically requires an FCP. As far as I understand, these macros are ancient left-overs from builtin support for rustc-serialize. We don't even show these in the nightly docs anymore. Let's mark them as deprecated. @rfcbot merge |
Team member @m-ou-se has proposed to merge this. The next step is review by the rest of the tagged team members: No concerns currently listed. Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up! See this document for info about what commands tagged team members can give me. |
This comment has been minimized.
This comment has been minimized.
852d04e
to
924e522
Compare
Wow. I'm surprised these haven't been deprecated yet. These were indeed ancient leftovers from the pre-serde era of automatic type driven serialization. IIRC, their names were specifically prefixed with |
🔔 This is now entering its final comment period, as per the review above. 🔔 |
Likely only due to technical limitations, I seem to recall @petrochenkov making it so all of the builtin macros have a presence in the standard library (even w/o any body), at some point in the last couple years. |
Seems a bit overkill to wait for a 10 day FCP (and miss the release cycle) for a simple long-overdue deprecation. Marking the FCP as finished. |
Just to be sure, can we have a test that shows a deprecation warning? I'm worried the current system will only warn on a reexport (or at least an implicit import), not on any use of the derives. |
|
Thanks! Feels a bit strange that there were no preexisting tests that changed output, but maybe that's because such a test would need to get the library from ( |
@bors r+ |
📌 Commit 924e522 has been approved by |
…erives, r=petrochenkov Deprecate RustcEncodable and RustcDecodable. We can't remove the `RustcEncodable` and `RustcDecodable` derive macros from the prelude, but we can deprecate them.
Rollup of 10 pull requests Successful merges: - rust-lang#81822 (Added `try_exists()` method to `std::path::Path`) - rust-lang#83072 (Update `Vec` docs) - rust-lang#83077 (rustdoc: reduce GC work during search) - rust-lang#83091 (Constify `copy` related functions) - rust-lang#83156 (Fall-back to sans-serif if Arial is not available) - rust-lang#83157 (No background for code in portability snippets) - rust-lang#83160 (Deprecate RustcEncodable and RustcDecodable.) - rust-lang#83162 (Specify *.woff2 files as binary) - rust-lang#83172 (More informative diagnotic from `x.py test` attempt atop beta checkout) - rust-lang#83196 (Use delay_span_bug instead of panic in layout_scalar_valid_range) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
We can't remove the
RustcEncodable
andRustcDecodable
derive macros from the prelude, but we can deprecate them.