Skip to content

Conversation

ehuss
Copy link
Contributor

@ehuss ehuss commented May 27, 2020

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

Copy link
Contributor

@mark-i-m mark-i-m left a 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

Copy link
Contributor

@chrissimpkins chrissimpkins left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

Copy link
Contributor

@mark-i-m mark-i-m left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks again!

@mark-i-m mark-i-m merged commit d7067f1 into rust-lang:master May 28, 2020
Dylan-DPC-zz pushed a commit to Dylan-DPC-zz/rust that referenced this pull request May 29, 2020
…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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants