dwattttt 2 days ago

As sibling notes, it is. It's very rarely seen though.

One place you might see something like it is if an API takes ownership, but returns it on error; you see the error side carry the resource you gave it, so you could try again.

Reply View 0 replies
IshKebab a day ago

How is that different to

  Fn(_: &mut T)

?
Reply View 4 replies
  • Soft a day ago

    In the former the caller does not retain access to T until Fn returns.

    Reply View 3 replies
    • andyferris a day ago

      I think I'm lost. If I give a mutable reference to a function... I can't access it (even read it) until it returns, no?

      What is different?

      Reply View 1 reply
      • zbentley 7 hours ago

        Let's say a function "foo" calls "fn bar(_: &mut T) -> ()".

        When passing a mutable reference, the lifetime of the object is largely decided by "foo" (with some caveats).

        Now, let's say that "foo" instead calls "fn bar(_: T) -> T".

        When passing the object itself, the lifetime is largely decided/decide-able by "bar".

        Reply View 0 replies
    • IshKebab a day ago

      That's true of mutable references too though isn't it? In fact lots of people have suggested they should really have been called "exclusive references", since you can actually mutate some objects through non-exclusive references (called "interior mutability" normally).

      Reply View 0 replies