-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Allows moving in owned values into multiple closures #7444
Labels
I-crash
Issue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics.
Comments
More minimal test case is over in the referred bug. |
Interesting, hadn't seen this bug before. |
nikomatsakis
added a commit
to nikomatsakis/rust
that referenced
this issue
Jul 17, 2013
nikomatsakis
added a commit
to nikomatsakis/rust
that referenced
this issue
Jul 17, 2013
fixed by pull #7849 |
flip1995
pushed a commit
to flip1995/rust
that referenced
this issue
Oct 20, 2022
…=llogiq Add a suggestion and a note about orphan rules for `from_over_into` Adds a machine applicable suggestion to convert the `Into` impl into a `From` one to `from_over_into` Also adds a note explaining that `impl From<Local> for Foreign` is fine if the `Into` type is foreign Closes rust-lang#7444 Addresses half of rust-lang#9638 changelog: [`from_over_into`] Add a suggestion and a note about orphan rules
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
I-crash
Issue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics.
The following testcase crashes at runtime when call_f is called the second time. It appears rustc accepts to move the value t into "both" heap closures.
Tested with version f1e09d6 / rustc 0.6 (f1e09d6 2013-06-26 23:07:41 -0700)
Assign to @bblum
The text was updated successfully, but these errors were encountered: