about summary refs log tree commit diff
path: root/tests/ui/rfcs/rfc-3348-c-string-literals
AgeCommit message (Collapse)AuthorLines
2025-09-26Ignore more failing ui tests for GCC backendGuillaume Gomez-0/+1
2024-11-27Update tests to use new proc-macro headerEric Huss-4/+1
2024-07-18Replace ASCII control chars with Unicode Control PicturesEsteban Küber-0/+0
``` error: bare CR not allowed in doc-comment --> $DIR/lex-bare-cr-string-literal-doc-comment.rs:3:32 | LL | /// doc comment with bare CR: '␍' | ^ ```
2024-02-16[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives许杰友 Jieyou Xu (Joe)-14/+14
2024-01-12Detect `NulInCStr` error earlier.Nicholas Nethercote-0/+0
By making it an `EscapeError` instead of a `LitError`. This makes it like the other errors produced when checking string literals contents, e.g. for invalid escape sequences or bare CR chars. NOTE: this means these errors are issued earlier, before expansion, which changes behaviour. It will be possible to move the check back to the later point if desired. If that happens, it's likely that all the string literal contents checks will be delayed together. One nice thing about this: the old approach had some code in `report_lit_error` to calculate the span of the nul char from a range. This code used a hardwired `+2` to account for the `c"` at the start of a C string literal, but this should have changed to a `+3` for raw C string literals to account for the `cr"`, which meant that the caret in `cr"` nul error messages was one short of where it should have been. The new approach doesn't need any of this and avoids the off-by-one error.
2023-12-09Tweak the `no-nuls.rs` test.Nicholas Nethercote-0/+0
The `empty!` macro calls should be outside the `cfg(FALSE)` function.
2023-11-01Stabilize C string literalsJohn Millikin-40/+0
2023-07-23add proc macro testDeadbeef-0/+30
2023-07-23reimplement C string literalsDeadbeef-88/+12
2023-07-05Add regression testLeón Orell Valerian Liehr-0/+24
2023-07-05Revert the lexing of c_str_literalsLeón Orell Valerian Liehr-16/+96
2023-05-02fix tidyDeadbeef-0/+0
2023-05-02make it semantic errorDeadbeef-0/+0
2023-05-02try gating early, add non-ascii testDeadbeef-0/+10
2023-05-02fix TODO commentsDeadbeef-0/+6
2023-05-02update and add a few testsDeadbeef-0/+35