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

Decide on (and implement) which parts of the AST can get stability attributes #687

Closed
steveklabnik opened this issue Jan 21, 2015 · 1 comment
Labels
T-lang Relevant to the language team, which will review and decide on the RFC.

Comments

@steveklabnik
Copy link
Member

Issue by huonw
Tuesday Sep 03, 2013 at 23:56 GMT

For earlier discussion, see rust-lang/rust#8967

This issue was labelled with: A-attributes, A-lint, B-RFC in the Rust repository


As of #8921, the compiler checks the attributes on structs, enum variants (not enums themselves) and functions. Definitely required: methods (#8961) and mods (#8962).

Up for discussion:

  • traits
  • enums
  • impls (both impl Type and impl Trait for Type)
  • struct fields
  • type aliases.
  • foreign fns
  • anything else that can take attributes in the ast

(Part of #6875.)

@petrochenkov
Copy link
Contributor

This is implemented long ago.
Everything that can be named is checked for stability, except for reexports (tracked by rust-lang/rust#23937).

@petrochenkov petrochenkov added T-lang Relevant to the language team, which will review and decide on the RFC. and removed A-wishlist labels Jan 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-lang Relevant to the language team, which will review and decide on the RFC.
Projects
None yet
Development

No branches or pull requests

2 participants