os-rust/tests/ui/str/str-escape.stderr

warning: multiple lines skipped by escaped newline
  --> $DIR/str-escape.rs:6:14
   |
LL |       let s = "\
   |  ______________^
LL | |
LL | |              ";
   | |_____________^ skipping everything up to and including this point

warning: whitespace symbol '\u{a0}' is not skipped
  --> $DIR/str-escape.rs:12:18
   |
LL |       let s = c"foo\
   |  __________________^
LL | |              bar
   | |   ^ whitespace symbol '\u{a0}' is not skipped
   | |___|
   |

warning: whitespace symbol '\u{c}' is not skipped
  --> $DIR/str-escape.rs:26:16
   |
LL |       let s = b"a\
   |  ________________^
LL | |     ␌b";
   | |     ^ whitespace symbol '\u{c}' is not skipped
   | |_____|
   |

warning: 3 warnings emitted
-												Add UI tests for string escape warnings.

											
										
										
											2021-08-11 12:13:24 +02:00
+								warning: multiple lines skipped by escaped newline
-												Avoid useless checking in `from_token_lit`.

The parser already does a check-only unescaping which catches all
errors. So the checking done in `from_token_lit` never hits.

But literals causing warnings can still occur in `from_token_lit`. So
the commit changes `str-escape.rs` to use byte string literals and C
string literals as well, to give better coverage and ensure the new
assertions in `from_token_lit` are correct.

											
										
										
											2024-01-22 16:58:39 +11:00
+								  --> $DIR/str-escape.rs:6:14
-												Add UI tests for string escape warnings.

											
										
										
											2021-08-11 12:13:24 +02:00
+								   |
 								LL |       let s = "\
 								   |  ______________^
 								LL | |
 								LL | |              ";
 								   | |_____________^ skipping everything up to and including this point
-												fix(lexer): not skipped whitespace warning for '\x0c'

											
										
										
											2023-03-09 22:42:06 +08:00
+								warning: whitespace symbol '\u{a0}' is not skipped
-												Avoid useless checking in `from_token_lit`.

The parser already does a check-only unescaping which catches all
errors. So the checking done in `from_token_lit` never hits.

But literals causing warnings can still occur in `from_token_lit`. So
the commit changes `str-escape.rs` to use byte string literals and C
string literals as well, to give better coverage and ensure the new
assertions in `from_token_lit` are correct.

											
										
										
											2024-01-22 16:58:39 +11:00
+								  --> $DIR/str-escape.rs:12:18
-												Add UI tests for string escape warnings.

											
										
										
											2021-08-11 12:13:24 +02:00
+								   |
-												Avoid useless checking in `from_token_lit`.

The parser already does a check-only unescaping which catches all
errors. So the checking done in `from_token_lit` never hits.

But literals causing warnings can still occur in `from_token_lit`. So
the commit changes `str-escape.rs` to use byte string literals and C
string literals as well, to give better coverage and ensure the new
assertions in `from_token_lit` are correct.

											
										
										
											2024-01-22 16:58:39 +11:00
+								LL |       let s = c"foo\
 								   |  __________________^
-												Add UI tests for string escape warnings.

											
										
										
											2021-08-11 12:13:24 +02:00
+								LL | |              bar
-												fix(lexer): not skipped whitespace warning for '\x0c'

											
										
										
											2023-03-09 22:42:06 +08:00
+								   | |   ^ whitespace symbol '\u{a0}' is not skipped
-												Add UI tests for string escape warnings.

											
										
										
											2021-08-11 12:13:24 +02:00
+								   | |___|
-												tests: remove some trailing ws

											
										
										
											2024-04-25 13:17:29 +03:00
+								   |
-												Add UI tests for string escape warnings.

											
										
										
											2021-08-11 12:13:24 +02:00
-												fix(lexer): not skipped whitespace warning for '\x0c'

											
										
										
											2023-03-09 22:42:06 +08:00
+								warning: whitespace symbol '\u{c}' is not skipped
-												Avoid useless checking in `from_token_lit`.

The parser already does a check-only unescaping which catches all
errors. So the checking done in `from_token_lit` never hits.

But literals causing warnings can still occur in `from_token_lit`. So
the commit changes `str-escape.rs` to use byte string literals and C
string literals as well, to give better coverage and ensure the new
assertions in `from_token_lit` are correct.

											
										
										
											2024-01-22 16:58:39 +11:00
+								  --> $DIR/str-escape.rs:26:16
-												fix(lexer): not skipped whitespace warning for '\x0c'

											
										
										
											2023-03-09 22:42:06 +08:00
+								   |
-												Avoid useless checking in `from_token_lit`.

The parser already does a check-only unescaping which catches all
errors. So the checking done in `from_token_lit` never hits.

But literals causing warnings can still occur in `from_token_lit`. So
the commit changes `str-escape.rs` to use byte string literals and C
string literals as well, to give better coverage and ensure the new
assertions in `from_token_lit` are correct.

											
										
										
											2024-01-22 16:58:39 +11:00
+								LL |       let s = b"a\
 								   |  ________________^
-												Replace ASCII control chars with Unicode Control Pictures

```
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-07-09 16:46:09 +00:00
+								LL | |     ␌b";
-												Be more accurate about calculating `display_col` from a `BytePos`

No longer track "zero-width" chars in `SourceMap`, read directly from the line when calculating the `display_col` of a `BytePos`. Move `char_width` to `rustc_span` and use it from the emitter.

This change allows the following to properly align in terminals (depending on the font, the replaced control codepoints are rendered as 1 or 2 width, on my terminal they are rendered as 1, on VSCode text they are rendered as 2):

```
error: this file contains an unclosed delimiter
  --> $DIR/issue-68629.rs:5:17
   |
LL | ␜␟ts␀![{i
   |       -- unclosed delimiter
   |       |
   |       unclosed delimiter
LL | ␀␀  fn rݻoa>rݻm
   |                ^
```

											
										
										
											2024-07-09 17:00:19 +00:00
+								   | |     ^ whitespace symbol '\u{c}' is not skipped
 								   | |_____|
-												tests: remove some trailing ws

											
										
										
											2024-04-25 13:17:29 +03:00
+								   |
-												fix(lexer): not skipped whitespace warning for '\x0c'

											
										
										
											2023-03-09 22:42:06 +08:00
 								warning: 3 warnings emitted
-												Add UI tests for string escape warnings.

											
										
										
											2021-08-11 12:13:24 +02:00