about summary refs log tree commit diff
path: root/library/std/src/sys/unix/stack_overflow.rs
diff options
context:
space:
mode:
authorDylan DPC <dylan.dpc@gmail.com>2020-06-02 18:29:57 +0200
committerGitHub <noreply@github.com>2020-06-02 18:29:57 +0200
commit466d3e702a0626305f32b3230b206f4f2b650bfc (patch)
treee06987596754c4b63d9714aad2b996167768cdf8 /library/std/src/sys/unix/stack_overflow.rs
parenteeaf497b2a6bc065874e3d3367b1f3023c5bb3d3 (diff)
parent7be8077b3fe7565573001b602f8709467da903e7 (diff)
downloadrust-466d3e702a0626305f32b3230b206f4f2b650bfc.tar.gz
rust-466d3e702a0626305f32b3230b206f4f2b650bfc.zip
Rollup merge of #72884 - Julian-Wollersberger:raw_str_error_cleanup, r=petrochenkov
RawString error reporting cleanup

I simplified how errors with raw string are represented in the lexer and reportet in the parser, by using one enum instead of two structs with impls. This makes 70 code lines obsolete.

I also noticed some other things (2nd commit) and added a missing test for the `too many '#' symbols' error.

My original intent was to improve performance, but the only thing I found was to inline some functions in `cursor.rs`. It's effect is barely measurable, though.

There is one open question. Before, the compiler aborts when encountering the `too many '#' symbols` error. Now the lexer says in this case that there are 0 hashes, and then later the parser aborts on the error.
I'm worrying that the parser may be changed to recover and continue, and then later stages will see the wrong numer of hashes and act strange. (eg. the `format!` macro expansion).
Is that possibility important enough today to worry about it?
Diffstat (limited to 'library/std/src/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions