about summary refs log tree commit diff
path: root/tests/ui/impl-trait/precise-capturing
AgeCommit message (Collapse)AuthorLines
2024-07-11Suggest using precise capturing for hidden type that captures regionMichael Goulet-3/+100
2024-06-28Move binder and polarity parsing into parse_generic_ty_boundMichael Goulet-0/+112
2024-06-24Deny use<> for RPITITsMichael Goulet-45/+76
2024-06-20Add a test demonstrating that RPITITs cant use precise capturingMichael Goulet-0/+63
2024-06-17Delay a bug and mark precise_capturing as not incompleteMichael Goulet-225/+45
2024-06-17Detect duplicatesMichael Goulet-0/+39
2024-06-17Add tests for illegal use bound syntaxMichael Goulet-2/+119
2024-06-17Rework precise capturing syntaxMichael Goulet-124/+124
2024-06-17Make parse_seq_to_before_tokens take expected/nonexpected tokens, use in ↵Michael Goulet-10/+1
parse_precise_capturing_syntax
2024-05-13And finally add testsMichael Goulet-0/+133
2024-05-13Warn against redundant use<...>Michael Goulet-1/+71
2024-04-23Rollup merge of #124169 - compiler-errors:parser-fatal, r=oli-obkMatthias Krüger-0/+25
Don't fatal when calling `expect_one_of` when recovering arg in `parse_seq` In `parse_seq`, when parsing a sequence of token-separated items, if we don't see a separator, we try to parse another item eagerly in order to give a good diagnostic and recover from a missing separator: https://github.com/rust-lang/rust/blob/d1a0fa5ed3ffe52d72f761d3c95cbeb0a9cdfe66/compiler/rustc_parse/src/parser/mod.rs#L900-L901 If parsing the item itself calls `expect_one_of`, then we will fatal because of #58903: https://github.com/rust-lang/rust/blob/d1a0fa5ed3ffe52d72f761d3c95cbeb0a9cdfe66/compiler/rustc_parse/src/parser/mod.rs#L513-L516 For `precise_capturing` feature I implemented, we do end up calling `expected_one_of`: https://github.com/rust-lang/rust/blob/d1a0fa5ed3ffe52d72f761d3c95cbeb0a9cdfe66/compiler/rustc_parse/src/parser/ty.rs#L712-L714 This leads the compiler to fatal *before* having emitted the first error, leading to absolutely no useful information for the user about what happened in the parser. This PR makes it so that we stop doing that. Fixes #124195
2024-04-20Explicitly mention `Self`Michael Goulet-5/+5
2024-04-20Flip spans for precise capturing syntax not capturing a ty/ct paramMichael Goulet-14/+16
2024-04-19Fix capturing duplicated lifetimes via parentMichael Goulet-0/+66
2024-04-19Don't fatal when calling expect_one_of when recovering arg in parse_seqMichael Goulet-0/+25
2024-04-15More polishingMichael Goulet-1/+53
2024-04-15Use a path instead of an ident (and stop manually resolving)Michael Goulet-14/+24
2024-04-15Some ordering and duplication checksMichael Goulet-0/+53
2024-04-15Add hir::Node::PreciseCapturingNonLifetimeArgMichael Goulet-31/+68
2024-04-15Validation and other thingsMichael Goulet-1/+203
2024-04-15Begin AST lowering for precise capturesMichael Goulet-0/+56