Uh oh!
There was an error while loading. Please reload this page.
Better handling of tab in error - #33513
Conversation
rust-highfive
commented
May 9, 2016
(rust_highfive has picked a reviewer for you, use r? to override) |
sanxiyn
commented
May 9, 2016
Ugh, this failed tidy because of (intentional) tab characters. |
nikomatsakis
commented
May 11, 2016
thanks @sanxiyn! I'll take a look soon. |
nikomatsakis
commented
May 11, 2016
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). |
sanxiyn
commented
May 12, 2016
Changed to use We could do something more fancy later. This is simply restoring the longstanding behavior introduced in fd98ea8, thereby fixing the regression. |
nikomatsakis
commented
May 12, 2016
Yeah, good for now. Thanks @sanxiyn ! :) |
nikomatsakis
commented
May 12, 2016
@bors r+ |
bors
commented
May 12, 2016
📌 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.
bors
commented
May 13, 2016
⌛ Testing commit c331032 with merge edb6f83... |
Better handling of tab in error cc #33240.
cc #33240.