I was referring to Unpin.
-
I guess I understand it a bit differently. Take string constants, for example. We already had the idea of memory that is more static. This just takes a concept that existed implicitly and made it more explicit.
Yeah, as nervous as I am about generators, async/await, and language feature creep, I think non-movability is just peeling off an implicit aspect of statics (and surfaces elsewhere, eg. in unsafe code that's informally sensitive to pointer identity / movement)
-
-
That's true, so it probably has more benefits other than just generators, I buy that. Re feature creep, it looks like the Rubyfication of Rust is getting out of hand… I really hope we won't end up being C++ 2.0 with every single programmer shoving in their own niche feature.
-
It's a tough call. I basically spent the final year I was involved in the project saying no to things, and it didn't really endear me to anyone, nor fix the problems people were trying to solve with all the things I was resisting.
-
While I agree that languages frequently add more features than is healthy for them, I also sympathize with the difficulty of saying exactly _where_ to stop. Last conversation I had like this ended with the metaphor "approach an asymptote".
-
There’s no language semantics in Unpin. These types can be moved just like any other; the Pin type’s API just doesn’t support moving a !Unpin type out of it
-
I thought this was the end of the thread, my tweet isn’t directly connected to Graydon’s immediately prior tweet
-
Anyway this criticism seems misinformed to me. We specifically did *not* add any language level notion of IMO ability, it’s all library code implemented in terms of existing features
-
*immovabllity not IMO ability
End of conversation
New conversation -
-
-
(I mean I personally think it would have been nice to keep traits as a dispatch thing alone, keep them out of the role of hooks for special judgements the compiler gets to make; but that ship sailed ages ago, the "shift compiler logic to libraries" argument won)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.