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: How to deal with bugs in rustc? #32

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

Policy: How to deal with bugs in rustc? #32

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 document actual rustc behavior (including bugs)? Or should it document the intended behavior? Or both?

Related: If there is a known issue, should it be encouraged or discouraged to link to the GitHub issue?

  • ehuss's preference is to never link to issues.

Related: Should it have specific callouts for future-incompatible warnings?
How should these known problems be documented? Should it document how it is intended to work? What if the intention is not yet known?
@ehuss ehuss mentioned this issue Mar 1, 2024
Open
@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