News for hackers. Stuff that matters.
Re:Unsoundness in Pin by jeltz on Friday November 29, 2019 @11:08AM (#21665134)
> Before Rust 1.0 it wasn't clear that such a concept of "unmoveability" would be generally useful. [...]

Hm, I ran into quite a lot of cases where I wanted Pin or something similar when porting a C program to Rust, and if I recall correctly also the creator of vulkano also ran into plenty of cases when writing it, so I am a bit surprised people did not realize this. My case was a program which in its C version was based around an epoll event loop, so maybe that is a bit similar to the async/generators issue.

Re:Unsoundness in Pin by kibwen on Friday November 29, 2019 @11:15AM (#21665163)
I could have perhaps written "would be generally useful enough to justify the additional annotation burden" (alluded to later in the paragraph). Also, in what year were you discovering these use cases? The discussions in question would have had to have happened in 2014 or earlier; for people who began using Rust post-1.0, it may very well be that these use cases were encountered because the language was stable by then, and that people might not have bothered enough with an unstable language to bother pushing the language to its limits like this. Though I guess we can take solace in the idea that the language that comes after Rust someday might benefit from these case studies. :)
Re:Unsoundness in Pin by jeltz on Friday November 29, 2019 @11:17AM (#21665174)
You are very correct in your guess that it was post-1.0, it is like you can read my mind. :) I would indeed not have bothered to port my production code to a non-stable language. But once I started doing that I ran into these issues quite quickly.