Skip to content
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 rustc-serialize attribute #42449

Closed
brson opened this issue Jun 5, 2017 · 7 comments
Closed

Deprecate rustc-serialize attribute #42449

brson opened this issue Jun 5, 2017 · 7 comments
Labels
C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC I-needs-decision Issue: In need of a decision. T-lang Relevant to the language team, which will review and decide on the PR/issue.

Comments

@brson
Copy link
Contributor

brson commented Jun 5, 2017

AFAIK the attribute itself is still undeprecated. Just filing an issue to track it.

@brson brson added I-needs-decision Issue: In need of a decision. T-lang Relevant to the language team, which will review and decide on the PR/issue. labels Jun 5, 2017
@brson brson changed the title Deprecatet rustc-serialize attribute Deprecate rustc-serialize attribute Jun 5, 2017
@brson
Copy link
Contributor Author

brson commented Jun 5, 2017

Can this be don for 1.20?

@eddyb
Copy link
Member

eddyb commented Jun 6, 2017

Do you mean the RustcEncodable and RustcDecodable derives? Or something else?

@brson
Copy link
Contributor Author

brson commented Jul 8, 2017

@eddyb Er yes that's what I mean.

@Mark-Simulacrum
Copy link
Member

I believe on the implementation side technically https://github.com/rust-lang/rust/blob/master/src/libsyntax_ext/deriving/mod.rs#L119 is what needs to change, but it's worth noting that the Rust compiler itself rather extensively uses these attributes: ~430 of each excluding tests currently, I believe. Maybe it is too early to do this? Or perhaps these attributes are different in some way?

@eddyb
Copy link
Member

eddyb commented Jul 8, 2017

If the traits from the crates.io library are deprecated instead of the derives, and rustc's copy of the library is left untouched, I believe the derives will trigger the deprecation warnings, but only for users of the crates.io library and Rust won't have a thousand errors while building.

@Mark-Simulacrum Mark-Simulacrum added the C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC label Jul 27, 2017
@leroycep
Copy link

Is this still an issue?

@Centril
Copy link
Contributor

Centril commented Sep 15, 2018

Closing in favor of rust-lang-deprecated/rustc-serialize#193.

@Centril Centril closed this as completed Sep 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC I-needs-decision Issue: In need of a decision. T-lang Relevant to the language team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

5 participants