-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Better handling of tab in error #33513
Conversation
(rust_highfive has picked a reviewer for you, use r? to override) |
Ugh, this failed tidy because of (intentional) tab characters. |
thanks @sanxiyn! I'll take a look soon. |
I think you can just change the string constant to use a multi-line string I took a quick look at the PR. I'll look a bit more deeply in a bit. This seems like an improvement over the status quo, though I had contemplated some more radical approaches -- for example modifying the source text to convert tabs to spaces, and adjusting column numbers in the annotations appropriately, or maintaining some more complex mapping (the aim there would be to also handle unicode characters more gracefully, I think we have some challenges there still based on the unicode-input tests). |
Changed to use We could do something more fancy later. This is simply restoring the longstanding behavior introduced in fd98ea8, thereby fixing the regression. |
Yeah, good for now. Thanks @sanxiyn ! :) |
@bors r+ |
📌 Commit c331032 has been approved by |
Better handling of tab in error cc rust-lang#33240.
Better handling of tab in error cc rust-lang#33240.
⌛ Testing commit c331032 with merge edb6f83... |
Better handling of tab in error cc #33240.
cc #33240.