-
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
tests for cleanup in guards #3478
Comments
Not critical for 0.6; de-milestoning |
Nominating for milestone 5, production-ready. |
accepted for well-covered milestone |
Nominating for discussion with @nikomatsakis present. |
P-low, not a blocker. |
I don't see any tests for this still, though I'm not sure if this is refering to the no-longer-allowed ability to move from the matched value in the guard (which does have tests). |
/cc @nikomatsakis : what do you think of what @cmr is saying? |
Triage: this ticket is incredibly old at this point. I'm going to assume @cmr is right. @nikomatsakis if you think that's wrong, please re-open with the correct context. |
implement support for __rust_alloc_error_handler Fixes rust-lang/miri#3439
I realized I forgot to ensure that there are tests for cleanup of by-value bindings in match guards. For example, if the guard should fail, or be false, we have to be sure we don't leak. Similarly, just testing that if the guard is taken, cleanup occurs---there may not be good dedicated tests for that either.
The text was updated successfully, but these errors were encountered: