-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
error: internal compiler error: unexpected region in query response: ReScope(Destruction(219))
#60127
Comments
One quick note: This is GitHub. It is meant for sharing code, but yet you share your code via google drive? :| (please don't get me wrong! Thanks for reporting the issue, but that bugged me ^^) |
Sorry, it's a private project on gitlab. There's not a lot there yet so I didn't mind posting the code here as a zip file. If anyone needs access via gitlab to look into this I'd be happy to provide it |
You could have created a new repo at GitHub/GitLab ;) As said, thanks again! |
Good point, I should have thought of that |
It seems like what we really need here is to reduce this to a smaller, standalone test case -- or at minimum to bisect the failure to a particular PR, perhaps using https://github.com/rust-lang-nursery/cargo-bisect-rustc. |
Sadly I haden't time yet to look into it :| If somebody comes up with a MCVE I will happily bisect it |
Would seeing the diff between the working code and failing code help at all? |
…r=pnkfelix Constrain all regions in the concrete type for an opaque type `push_outlives_components` skips some regions in a type, notably the signature of a closure is ignored. Most of the time this is OK, but for opaque types the concrete type is used when checking auto-trait bounds in other functions. cc @nikomatsakis @pnkfelix Closes rust-lang#57464 Closes rust-lang#60127
…r=pnkfelix Constrain all regions in the concrete type for an opaque type `push_outlives_components` skips some regions in a type, notably the signature of a closure is ignored. Most of the time this is OK, but for opaque types the concrete type is used when checking auto-trait bounds in other functions. cc @nikomatsakis @pnkfelix Closes rust-lang#57464 Closes rust-lang#60127
…r=pnkfelix Constrain all regions in the concrete type for an opaque type `push_outlives_components` skips some regions in a type, notably the signature of a closure is ignored. Most of the time this is OK, but for opaque types the concrete type is used when checking auto-trait bounds in other functions. cc @nikomatsakis @pnkfelix Closes rust-lang#57464 Closes rust-lang#60127
…r=pnkfelix Constrain all regions in the concrete type for an opaque type `push_outlives_components` skips some regions in a type, notably the signature of a closure is ignored. Most of the time this is OK, but for opaque types the concrete type is used when checking auto-trait bounds in other functions. cc @nikomatsakis @pnkfelix Closes rust-lang#57464 Closes rust-lang#60127
I went through the process of updating one of my projects from actix-web 0.7 to 1.0 and ran into a compiler bug. I'm not sure what is causing the issue because I had to change a lot of code to get to this point. Cargo check passes but cargo run produces the provided backtrace.
Here is a link to the project that produces the issue:
Source Code
Meta
rustc 1.34.0 (91856ed 2019-04-10)
binary: rustc
commit-hash: 91856ed
commit-date: 2019-04-10
host: x86_64-unknown-linux-gnu
release: 1.34.0
LLVM version: 8.0
Backtrace:
The text was updated successfully, but these errors were encountered: