News for hackers. Stuff that matters.

A comment on Unsoundness in Pin. Parent comment

Re:Unsoundness in Pin by creatonez on Friday November 29, 2019 @01:00PM (#21665813)
I don't get why we don't just use the same magic that `?Sized` uses, to make it opt-out in terms of mental overhead for the developer, but opt-in in terms of what's going on under the hood:

    #[derive(!Move)]
[ Parent | on HN ]
Re:Unsoundness in Pin by jeltz on Friday November 29, 2019 @01:16PM (#21665902)
Maybe this wont work for Move speficially, but I like this a solution for the general problem of skipping default traits.
[ Parent | on HN ]
Re:Unsoundness in Pin by withoutboats on Sunday December 01, 2019 @07:02PM (#21678712)
The syntax is different but Rust has this feature- its called auto traits, and its how we handle traits related to threadsafety. Its not a solution for what Pin solves because the whole notion that a type might be moveable or not moveable is actually a misstatement of the problem that Pin is solving.
[ Parent | on HN ]