You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Auto merge of #146375 - matthiaskrgr:rollup-utik9zj, r=matthiaskrgr
Rollup of 6 pull requests
Successful merges:
- #145463 (Reject invalid literal suffixes in tuple indexing, tuple struct indexing, and struct field name position)
- #145929 (fix APITIT being treated as a normal generic parameter in suggestions)
- #146001 (Update getopts to remove unicode-width dependency)
- #146365 (triagebot: warn about #[rustc_intrinsic_const_stable_indirect])
- #146366 (add approx_delta to all gamma tests)
- #146373 (fix comments about trait solver cycle heads)
r? `@ghost`
`@rustbot` modify labels: rollup
Copy file name to clipboardExpand all lines: compiler/rustc_parse/messages.ftl
-3Lines changed: 0 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -479,9 +479,6 @@ parse_invalid_identifier_with_leading_number = identifiers cannot start with a n
479
479
480
480
parse_invalid_literal_suffix_on_tuple_index = suffixes on a tuple index are invalid
481
481
.label = invalid suffix `{$suffix}`
482
-
.tuple_exception_line_1 = `{$suffix}` is *temporarily* accepted on tuple index fields as it was incorrectly accepted on stable for a few releases
483
-
.tuple_exception_line_2 = on proc macros, you'll want to use `syn::Index::from` or `proc_macro::Literal::*_unsuffixed` for code that will desugar to tuple field access
484
-
.tuple_exception_line_3 = see issue #60210 <https://github.com/rust-lang/rust/issues/60210> for more information
485
482
486
483
parse_invalid_logical_operator = `{$incorrect}` is not a logical operator
487
484
.note = unlike in e.g., Python and PHP, `&&` and `||` are used for logical operators
0 commit comments