You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A-linkageArea: linking into static, shared libraries and binariesE-easyCall for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
In general, the most helpful test case for reproducing a bug is one that the person reading the issue can copy and paste into a new file and compile with no extra effort. If it's a cross-crate bug, provide the contents of each file. It's usually not much extra effort to do this and it saves time for the person reading the bug report days or weeks later :-)
The test case I made up based on the template above compiles without error. I'm checking it in, but I'm not sure whether the bug was accidentally fixed or whether my test case was wrong. I'm closing this, but feel free to reopen if you have a stand-alone test case that reproduces the bug.
A-linkageArea: linking into static, shared libraries and binariesE-easyCall for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
rust: upcall fail 'lookup_item: id not found: 52136', /home/bblum/rust/src/rustc/metadata/decoder.rs:96
error: internal compiler error: unexpected failure
Code that worked fine looked like:
unsafe fn ... {
unsafe fn ... { ... }
...map {|...|
...
}
}
Code that produced the crash:
unsafe fn ... {
...map {|...|
unsafe fn ... { ... }
...
}
}
Didn't bother testing without the 'unsafe's.
The text was updated successfully, but these errors were encountered: