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
I've been following your proposal on Claim. An unexpected benefit from add Claim may be actually impacting how and what rustc decides to do to Copy values.
In my recent issue, a comment says the behavior that is conservative may be due to the aversion to copy large Copy values. The reason is fair enough but the behavior is a quirk nonetheless. So, then I thought, maybe when Claim is implemented, some large values are not Claim then the compiler can be safely ensured that it's not copying a large value, say [u8; 1024] so that it can just claim or copy a value for me in the case of my issue.
The text was updated successfully, but these errors were encountered:
I've been following your proposal on
Claim
. An unexpected benefit from addClaim
may be actually impacting how and what rustc decides to do toCopy
values.In my recent issue, a comment says the behavior that is conservative may be due to the aversion to copy large
Copy
values. The reason is fair enough but the behavior is a quirk nonetheless. So, then I thought, maybe whenClaim
is implemented, some large values are notClaim
then the compiler can be safely ensured that it's not copying a large value, say[u8; 1024]
so that it can just claim or copy a value for me in the case of my issue.The text was updated successfully, but these errors were encountered: