News for hackers. Stuff that matters.
Re:Rust project goals: Immobile types and guaranteed destruc... by simonask on Monday August 03, 2026 @08:46AM (#49155049)
I guess `!Move` is largely equivalent to `Unpin` for the purposes of `Pin`, so for example Pin's safe constructor `Pin::new()` can be re-expressed in terms of `!Move` instead of `Unpin`. Today you need unsafe code to pin a `!Unpin` (i.e. "movable") type.

But I also suspect there are important differences between `!Move` and `Unpin` that I'm not sure about.

Re:Rust project goals: Immobile types and guaranteed destruc... by stymaar on Monday August 03, 2026 @02:46PM (#49159824)
This whole thread summarizes what's wrong with Pin: it's so confusing everyone in here got something wrong. (Just to address your mistake in particular Unpin is almost the opposite of !Move: it's the trait that represents things that can be un-pinned, that is: moved despite having been pinned. See https://doc.rust-lang.org/std/pin/index.html#unpin).
Re:Rust project goals: Immobile types and guaranteed destruc... by simonask on Tuesday August 04, 2026 @03:48AM (#49165525)
Right, of course. Yeah, it's an API riddled with so many double negatives it's hard to keep track.