-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
&fn is non-copyable #3904
Labels
Milestone
Comments
ghost
assigned nikomatsakis
Dec 4, 2012
Careful about &once fn etc. |
Reproduced with 737e115 (though the error is now "moving out of mutable field", it reflects the same issue). |
nikomatsakis
added a commit
to nikomatsakis/rust
that referenced
this issue
Feb 7, 2013
correct handling of moves for struct-record update. Part of rust-lang#3678. Fixes rust-lang#2828, rust-lang#3904, rust-lang#4719.
This is fixed. |
RalfJung
pushed a commit
to RalfJung/rust
that referenced
this issue
Oct 5, 2024
Refactor ``return_read_bytes_and_count`` and ``return_written_byte_count_or_error`` Fixes rust-lang#3904 This PR - separate the error logic from ``return_read_bytes_and_count`` and ``return_written_byte_count_or_error`` into a helper function ``set_last_error_and_return``.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This test suggests that
&fn
is noncopyable. I do not believe this should be the case.The test yields:
The text was updated successfully, but these errors were encountered: