diff options
| author | bors <bors@rust-lang.org> | 2013-09-19 21:46:45 -0700 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2013-09-19 21:46:45 -0700 |
| commit | 7f826cb25ac3c1295a90bc8eb16e1cdf518fc6e1 (patch) | |
| tree | 2be92973440fb858516695621584587bbe0afe15 /src/rustllvm/RustWrapper.cpp | |
| parent | 407d179f4e0b625e6911ebaf72c87cd35935fb06 (diff) | |
| parent | 567c567b2dabbab9d74cf565b252e5024900e290 (diff) | |
| download | rust-7f826cb25ac3c1295a90bc8eb16e1cdf518fc6e1.tar.gz rust-7f826cb25ac3c1295a90bc8eb16e1cdf518fc6e1.zip | |
auto merge of #9308 : ben0x539/rust/lexer-error-spans, r=alexcrichton
Previously, the lexer calling `rdr.fatal(...)` would report the span of the last complete token, instead of a span within the erroneous token (besides one span fixed in 1ac90bb). This branch adds wrappers around `rdr.fatal(...)` that sets the span explicilty, so that all fatal errors in `libsyntax/parse/lexer.rs` now report the offending code more precisely. A number of tests try to verify that, though the `compile-fail` testing setup can only check that the spans are on the right lines, and the "unterminated string/block comment" errors can't have the line marked at all, so that's incomplete. This closes #9149. Also, the lexer errors now report the offending code in the error message, not just via the span, just like other errors do.
Diffstat (limited to 'src/rustllvm/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions
