Extend bindings_after_at (b1 @ Some(b2)
) tests with nested or_patterns
#67311
Labels
A-testsuite
Area: The testsuite used to check the correctness of rustc
C-enhancement
Category: An issue proposing an enhancement or a PR with one.
E-easy
Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
E-medium
Call for participation: Medium difficulty. Experience needed to fix: Intermediate.
F-bindings_after_at
`#![feature(bindings_after_at)]`
F-or_patterns
`#![feature(or_patterns)]`
F-slice_patterns
`#![feature(slice_patterns)]`
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Once
#![feature(or_patterns)]
(#54883), i.e.pat_0 | ... | pat_n
in nested positions, e.g.Some(Ok(a) | Err(b))
have progressed sufficiently in their implementation, e.g. when the MIR building implementation is done, we should extend the test suite for#![feature(bindings_after_at)]
(#65490), e.g.b1 @ Some(b2)
, to exercise the combination of these two features. Ideally, we would also account for the combination of those two with#![feature(slice_patterns)]
(#62254) and#![feature(box_patterns)]
(#29641) as well to make things really air-tight.This issue has been assigned to @thekuom via this comment.
The text was updated successfully, but these errors were encountered: