-
Notifications
You must be signed in to change notification settings - Fork 13k
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
unwrap
function documentation don't mention implicit copyability
#9099
Labels
E-easy
Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Comments
nominating production ready |
Just a bug |
We should probably not use the term |
Visiting for triage. Still a problem. |
We still say move: http://doc.rust-lang.org/core/option/type.Option.html#method.unwrap |
steveklabnik
added a commit
to steveklabnik/rust
that referenced
this issue
Aug 18, 2014
bors
added a commit
that referenced
this issue
Aug 18, 2014
flip1995
pushed a commit
to flip1995/rust
that referenced
this issue
Jul 18, 2022
…n-some, r=flip1995 Extend unnecessary_lazy_eval to cover `bool::then` -> `bool::then_some` fixes rust-lang#9097 changelog: Extend `unnecessary_lazy_eval` to convert `bool::then` to `bool::then_some`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
E-easy
Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
The documentation for Option unwrap (and possibly others) is currently wrong. It does not always move the value, since the value may be implicitly copyable. This needs to be mentioned in the docs, or the types that have
unwrap
methods should be annotated to make them not implicitly copyable (see #9098).The text was updated successfully, but these errors were encountered: