Yeah, there was. It was a difficult change. But to be fair I think that it is a reasonable concern - I think that the fact that we don't have copy constructors and therefore move/copy doesn't run arbitrary code is beneficial (although `.clone()` boilerplate is a downside)
I'd wager a lot of folks would be in favor of having `Arc` and `Rc` get auto cloned, though (probably fewer people if the cost was arbitrary copy constructors)
-
-
Arbitrary copy constructors are basically impossible to retrofit into rust without introducing a new ?-trait. It's not even a matter of cost there.
-
(the reason is unsafe code, for generic unsafe code to work you need to know when code you didn't write is allowed to execute)
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.