-
Notifications
You must be signed in to change notification settings - Fork 12.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make if let guard parsing consistent with normal guards #115371
Conversation
This is consistent with normal match guards.
@bors r+ |
⌛ Testing commit 89235fd with merge 82cd0ff640a6d93e92e52bd11bb20ac8071f3b06... |
The job Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
@bors r- bors synchronize fixing the queue |
@bors r=cjgillot |
…, r=cjgillot Make if let guard parsing consistent with normal guards - Add tests that struct expressions are not allowed in `if let` and `while let` (no change, consistent with `if` and `while`) - Allow struct expressions in `if let` guards (consistent with `if` guards). r? `@cjgillot` Closes rust-lang#93817 cc rust-lang#51114
☀️ Test successful - checks-actions |
Finished benchmarking commit (25283f4): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 628.364s -> 628.843s (0.08%) |
if let
andwhile let
(no change, consistent withif
andwhile
)if let
guards (consistent withif
guards).r? @cjgillot
Closes #93817
cc #51114