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.

Sign up for GitHub

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

Jump to bottom

Policy: Should deprecated things be called out? #33

Open
ehuss opened this issue Mar 1, 2024 · 0 comments
Open

Policy: Should deprecated things be called out? #33

ehuss opened this issue Mar 1, 2024 · 0 comments
Labels
C-meta Category: Meta discussion about the repository itself. We should refine each use of the policy label

Comments

@ehuss
Copy link
Contributor

ehuss commented Mar 1, 2024

Should the spec ever mention that some language construct is deprecated? For example, things that we know are deprecated, but will not be removed in an Edition, or whose replacement is not yet implemented or certain.

Similarly, if something is removed or changed in an Edition, should the Edition-specific docs mention that a particular thing is deprecated?

  • ehuss's preference is to not mention that for Edition-specific changes. Non-edition changes are a bit more difficult to make a judgement on.
@JoelMarcey JoelMarcey added the C-meta Category: Meta discussion about the repository itself. We should refine each use of the policy label label Mar 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C-meta Category: Meta discussion about the repository itself. We should refine each use of the policy label
Projects
Rust Specification: Tasks and Priorities
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ehuss @JoelMarcey