-
Notifications
You must be signed in to change notification settings - Fork 516
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
Add some guidelines on diagnostics. #716
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @ehuss! This is great :)
Some minor comments and clarifications requested below, but other than that r=me
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Co-authored-by: Who? Me?! <[email protected]> Co-authored-by: Chris Simpkins <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks again!
…omatsakis Remove rustc-ux-guidelines This is now in the rustc-dev-guide: * rust-lang/rustc-dev-guide#716 * rust-lang/rustc-dev-guide#717 This is a public page, but it was not linked to anywhere, so I think it is safe to remove. Google searches don't show it being used anywhere.
This is a start on adding some guidelines for diagnostics. I would love to see more input from those who actually work on diagnostics, but I figure this might help get the ball rolling.
This is sourced from several places (RFCs, comments, rustc-ux-guidelines), along with my own editorializing.
cc #14