-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Point at only one char on Span::next_point
#41174
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
Conversation
(rust_highfive has picked a reviewer for you, use r? to override) |
Travis found some issues by the way. |
6ed911b
to
db2f509
Compare
@estebank r=me once the errors are fixed |
Avoid pointing at two chars so the diagnostic output doesn't display a multiline span when starting beyond a line end.
@nikomatsakis fixed. Waiting on travis to confirm that I didn't introduce a different error. |
@bors r=nikomatsakis |
📌 Commit 4c80170 has been approved by |
⌛ Testing commit 4c80170 with merge bec5394... |
💔 Test failed - status-appveyor |
@bors retry |
Point at only one char on `Span::next_point` Avoid pointing at two chars so the diagnostic output doesn't display a multiline span when starting beyond a line end. Fix #41155. Instead of ```rust error: expected one of `(`, `const`, `default`, `extern`, `fn`, `type`, or `unsafe`, found `}` --> <anon>:3:1 | 1 | impl S { pub | _____________- starting here... 2 | | | | ...ending here: expected one of 7 possible tokens here 3 | } | ^ unexpected token ``` show ```rust error: expected one of `(`, `const`, `default`, `extern`, `fn`, `type`, or `unsafe`, found `}` --> <anon>:13:1 | 12 | pub | - expected one of 7 possible tokens here 13 | } | ^ unexpected token ```
☀️ Test successful - status-appveyor, status-travis |
Avoid pointing at two chars so the diagnostic output doesn't display a
multiline span when starting beyond a line end.
Fix #41155.
Instead of
show