I implemented this today. The rationale for making T represent
'pinned' is that 'pinned' is the broadest category -- all types can be
passed to a function expecting a pinned type. I still think that
making the default 'shared' is a good idea, but there are downsides --
it's easy to define a generic function or datatype as taking a more
narrow type than it really accepts.

Maybe we could have the compiler warn in such a case?
_______________________________________________
Rust-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/rust-dev

Reply via email to