Looks good. I'd like to include immutable records of implicitly copyable types as implicitly copyable.
> The primary use case for move mode arguments was to “give away” a unique > pointer: this is now achieved by having the callee simply declare a parameter > of unique type and having the caller move it to them. When doing channel communication or data-structure construction, there'll probably be a lot of calls that are 'giving away' arguments. I fear that requiring callers to annotate every one of them will be cumbersome. How about changing the semantics of by-move and by-copy parameters to simply automatically insert the copy/move annotation into every call? When exactly would you want to have functions with a non-single-word-sized return value not be constructor functions? I still feel we'd be better off trying to make this implicit and not exposing it to the user. _______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
