-
Notifications
You must be signed in to change notification settings - Fork 13.3k
ICE when building Iron #17694
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
Comments
I got this same ICE, here's a smaller example: #![feature(unboxed_closures)]
fn main() {
let x = 123i;
let _ = |&: | x;
} Backtrace:
|
This is unfortunate. I wonder if somebody can bisect and revert. Any changes to closure type checking recently that may have triggered this? |
I'm super new to rust, so I'll leave the reverting to you guys. I did do the bisect - the commit that introduced this is 2257e23 |
A work around (for @tomjakubowski's example at least) is using capture-by-move, e.g. #![feature(unboxed_closures)]
fn main() {
let x = 123i;
let _ = move |&: | x;
} |
That's what I tried in iron too, looks like it's working. |
Closing as a dupe of #17655. (Thanks for bisecting @jgallagher!) |
Repo: https://github.com/iron/iron
Master at this time: iron/iron@18c0981
Backtrace:
The text was updated successfully, but these errors were encountered: