Uh oh!
There was an error while loading. Please reload this page.
Clean up some diagnostics by making them more consistent - #68096
Merged
Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
varkorforce-pushed
the
diagnostic-cleanup
branch
from
January 10, 2020 21:18
85d5234 to
5cbd28dCompareCentril
reviewed
Jan 10, 2020
Centril
left a comment
Contributor
There was a problem hiding this comment.
r=me with comment addressed.
Uh oh!
There was an error while loading. Please reload this page.
varkorforce-pushed
the
diagnostic-cleanup
branch
from
January 10, 2020 22:25
5cbd28d to
498b586Compare
This comment has been minimized.
This comment has been minimized.
varkorforce-pushed
the
diagnostic-cleanup
branch
from
January 11, 2020 00:08
498b586 to
ba50587Compare
This comment has been minimized.
This comment has been minimized.
varkorforce-pushed
the
diagnostic-cleanup
branch
from
January 11, 2020 02:05
ba50587 to
6fd68a2Comparebors
commented
Jan 11, 2020
Collaborator
☔ The latest upstream changes (presumably #68115) made this pull request unmergeable. Please resolve the merge conflicts. |
varkorforce-pushed
the
diagnostic-cleanup
branch
from
January 11, 2020 11:51
6fd68a2 to
6ea4dbaComparevarkor
commented
Jan 11, 2020
ContributorAuthor
@bors r=Centril |
bors
commented
Jan 11, 2020
Collaborator
📌 Commit 6ea4dba has been approved by |
Centril added a commit
to Centril/rust
that referenced
this pull request
Jan 11, 2020
Clean up some diagnostics by making them more consistent In general: - Diagnostic should start with a lowercase letter. - Diagnostics should not end with a full stop. - Ellipses contain three dots. - Backticks should encode Rust code. I also reworded a couple of messages to make them read more clearly. It might be sensible to create a style guide for diagnostics, so these informal conventions are written down somewhere, after which we could audit the existing diagnostics. r? @Centril
JohnTitor added a commit
to JohnTitor/rust
that referenced
this pull request
Jan 11, 2020
Clean up some diagnostics by making them more consistent In general: - Diagnostic should start with a lowercase letter. - Diagnostics should not end with a full stop. - Ellipses contain three dots. - Backticks should encode Rust code. I also reworded a couple of messages to make them read more clearly. It might be sensible to create a style guide for diagnostics, so these informal conventions are written down somewhere, after which we could audit the existing diagnostics. r? @Centril
Centril added a commit
to Centril/rust
that referenced
this pull request
Jan 12, 2020
Clean up some diagnostics by making them more consistent In general: - Diagnostic should start with a lowercase letter. - Diagnostics should not end with a full stop. - Ellipses contain three dots. - Backticks should encode Rust code. I also reworded a couple of messages to make them read more clearly. It might be sensible to create a style guide for diagnostics, so these informal conventions are written down somewhere, after which we could audit the existing diagnostics. r? @Centril
bors
commented
Jan 12, 2020
Collaborator
☔ The latest upstream changes (presumably #67901) made this pull request unmergeable. Please resolve the merge conflicts. |
varkorforce-pushed
the
diagnostic-cleanup
branch
from
January 12, 2020 15:37
6ea4dba to
1faa05dComparevarkor
commented
Jan 12, 2020
ContributorAuthor
@bors r=Centril |
bors
commented
Jan 12, 2020
Collaborator
📌 Commit 1faa05d has been approved by |
Dylan-DPC-zz pushed a commit
to Dylan-DPC-zz/rust
that referenced
this pull request
Jan 12, 2020
Clean up some diagnostics by making them more consistent In general: - Diagnostic should start with a lowercase letter. - Diagnostics should not end with a full stop. - Ellipses contain three dots. - Backticks should encode Rust code. I also reworded a couple of messages to make them read more clearly. It might be sensible to create a style guide for diagnostics, so these informal conventions are written down somewhere, after which we could audit the existing diagnostics. r? @Centril
Dylan-DPC-zz pushed a commit
to Dylan-DPC-zz/rust
that referenced
this pull request
Jan 14, 2020
Clean up some diagnostics by making them more consistent In general: - Diagnostic should start with a lowercase letter. - Diagnostics should not end with a full stop. - Ellipses contain three dots. - Backticks should encode Rust code. I also reworded a couple of messages to make them read more clearly. It might be sensible to create a style guide for diagnostics, so these informal conventions are written down somewhere, after which we could audit the existing diagnostics. r? @Centril
Dylan-DPC-zz pushed a commit
to Dylan-DPC-zz/rust
that referenced
this pull request
Jan 15, 2020
Clean up some diagnostics by making them more consistent In general: - Diagnostic should start with a lowercase letter. - Diagnostics should not end with a full stop. - Ellipses contain three dots. - Backticks should encode Rust code. I also reworded a couple of messages to make them read more clearly. It might be sensible to create a style guide for diagnostics, so these informal conventions are written down somewhere, after which we could audit the existing diagnostics. r? @Centril
Dylan-DPC-zz pushed a commit
to Dylan-DPC-zz/rust
that referenced
this pull request
Jan 16, 2020
Clean up some diagnostics by making them more consistent In general: - Diagnostic should start with a lowercase letter. - Diagnostics should not end with a full stop. - Ellipses contain three dots. - Backticks should encode Rust code. I also reworded a couple of messages to make them read more clearly. It might be sensible to create a style guide for diagnostics, so these informal conventions are written down somewhere, after which we could audit the existing diagnostics. r? @Centril
bors added a commit
that referenced
this pull request
Jan 16, 2020
Rollup of 5 pull requests Successful merges: - #67780 (Move some queries from rustc::ty to librustc_ty.) - #68096 (Clean up some diagnostics by making them more consistent) - #68223 (Use 3.6 instead of 3.5 in float fract() documentation) - #68265 (Fix some issue numbers of unstable features) - #68266 (Changed docs for f32 and f64.) Failed merges: - #68204 (Use named fields for `{ast,hir}::ItemKind::Impl`) r? @ghost
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In general:
I also reworded a couple of messages to make them read more clearly.
It might be sensible to create a style guide for diagnostics, so these informal conventions are written down somewhere, after which we could audit the existing diagnostics.
r? @Centril