[rust-dev] Why doesn't rust require "mut" param prefix at call site?

Daniel Micay danielmicay at gmail.com
Wed Jan 1 22:21:07 PST 2014

On Thu, Jan 2, 2014 at 1:06 AM, Vadim <vadimcn at gmail.com> wrote:
> And let's not forget about the heap-allocated objects, which start out as pointers in the first place.

Unique pointers have value semantics so this shouldn't be relevant to
the visibility of mutation. The consensus is already to remove the
auto-coercion of `~T` to `&mut T` because it doesn't make any sense.
The auto-coercion to `&T` will probably either be removed or extended
to `T` too, but that hasn't been decided (or discussed much).

More information about the Rust-dev mailing list