> Not anymore, with the C decl. Can you elaborate on that?
> How about what I proposed earlier: the '+' sigil means by-value, the '&' > sigil means by-immutable-reference, and leaving it off has the compiler > choose a sensible default based on the type? That'd work, though it'd be a little obscure (a function fn<T>(T) will always take its arg by reference, even when instantiated with T=int). I guess it's a good stopgap until we decide what to do with monomorphizing. Would passing structural types by value be allowed? How would that look? (Using load/store as we used to do, or passing by pointer with the caller owning the value, or passed by pointer with the callee copying it into its frame?) _______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
