diff options
| author | Alex Crichton <alex@alexcrichton.com> | 2015-03-27 10:07:41 -0700 |
|---|---|---|
| committer | Alex Crichton <alex@alexcrichton.com> | 2015-03-27 10:07:41 -0700 |
| commit | b79fbe0dae488513e4fead02a7da84102d932749 (patch) | |
| tree | cb71fd4becff68bcda0543f943d93764d4c92c60 /src/test/codegen/stack-alloc-string-slice.rs | |
| parent | e42521aa58be928dd62b5450c443368d29ab6a65 (diff) | |
| parent | afaa3b6a2066e4dacd4e7dafb5fd911bf35bdd6c (diff) | |
| download | rust-b79fbe0dae488513e4fead02a7da84102d932749.tar.gz rust-b79fbe0dae488513e4fead02a7da84102d932749.zip | |
rollup merge of #23625: fhahn/issue-23620-ice-unicode-bytestring
closes #23620
This PR patches the issue mentioned in #23620, but there is also an ICE for invalid escape sequences in byte literals. This is due to the fact that the `scan_byte` function returns ` token::intern("??") ` for invalid bytes, resulting in an ICE later on. Is there a reason for this behavior? Shouldn't `scan_byte` fail when it encounters an invalid byte?
And I noticed a small inconsistency in the documentation. According to the formal byte literal definition in http://doc.rust-lang.org/reference.html#byte-and-byte-string-literals , a byte string literal contains `string_body *`, but according to the text (and the behavior of the lexer) it should not accept unicode escape sequences. Hence it should be replaced by `byte_body *`. If this is valid, I can add this fix to this PR.
Diffstat (limited to 'src/test/codegen/stack-alloc-string-slice.rs')
0 files changed, 0 insertions, 0 deletions