-
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
ICE: assertion failed: leak_check(infcx, &skol_map, snapshot).is_ok() #22872
Comments
I can't reproduce it on |
With
|
This isn't fixed yet. The tests that were added only pass because debug assertions are disabled when @bors tests stuff. |
@ebfull Can you elaborate on this? Does this still cause an ICE? On Saturday, September 12, 2015, Eduard Burtescu [email protected]
|
@apasel422 Yes, it always had, just that debug assertions became opt-in. |
Is there an issue open to get bors to run with debug assertions enabled, On Saturday, September 12, 2015, Eduard Burtescu [email protected]
|
Yes, we need to have bors checking with debug-assertions! (Or else we should just never use them in rustc, perhaps.) |
seems like the debug assertion is wrong because of #21974 |
maybe |
Based on the comments here, this should probably not be labeled E-needstest. |
Today, this produces the following, which is presumably correct? Either way, marking as E-needstest.
|
@Mark-Simulacrum Is that with debug assertions enabled? |
I think so. The way I check is with |
Add filtering option to `rustc_on_unimplemented` and reword `Iterator` E0277 errors - Add more targetting filters for arrays to `rustc_on_unimplemented` (Fix #53766) - Detect one element array of `Range` type, which is potentially a typo: `for _ in [0..10] {}` where iterating between `0` and `10` was intended. (Fix #23141) - Suggest `.bytes()` and `.chars()` for `String`. - Suggest borrowing or `.iter()` on arrays (Fix #36391) - Suggest using range literal when iterating on integers (Fix #34353) - Do not suggest `.iter()` by default (Fix #50773, fix #46806) - Add regression test (Fix #22872)
Add filtering option to `rustc_on_unimplemented` and reword `Iterator` E0277 errors - Add more targetting filters for arrays to `rustc_on_unimplemented` (Fix #53766) - Detect one element array of `Range` type, which is potentially a typo: `for _ in [0..10] {}` where iterating between `0` and `10` was intended. (Fix #23141) - Suggest `.bytes()` and `.chars()` for `String`. - Suggest borrowing or `.iter()` on arrays (Fix #36391) - Suggest using range literal when iterating on integers (Fix #34353) - Do not suggest `.iter()` by default (Fix #50773, fix #46806) - Add regression test (Fix #22872)
Code:
Output:
Rust version:
The text was updated successfully, but these errors were encountered: