Describe implicit copyability in documentation #7774
Comments
|
Way to steal my issue. I was so gonna post this >:[ /jk |
|
There isn't really a concept of implicit copyable, as it's just a term some people use to describe types that are not moved. I added documentation to the tutorial about this, and it is covered in the manual. http://static.rust-lang.org/doc/master/tutorial.html#move-semantics |
flip1995
pushed a commit
to flip1995/rust
that referenced
this issue
Oct 7, 2021
Useless exponent Closes rust-lang#7745 I'm open to some thoughts on dropping the exponents on suggestions when it's zero. I personally don't see any problem on this. changelog: [`useless_exponent`] suggestion drops exponent when exponent value is zero
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Neither the tutorial nor manual mention the implicit copyability in any detail. The tutorial should possibly at least mention it, and the manual should describe the conditions required for it.
The rule is possibly "primitive type like
int,float,()etc, or astruct/enumthat contains only implicitly copyable types, and doesn't have a destructor", but I'm not sure, so this should be checked with someone knowledgeable.The text was updated successfully, but these errors were encountered: