News for hackers. Stuff that matters.
Re:Speed of Rust vs. C by kibwen on Saturday March 13, 2021 @11:43AM (#26447719)
You have correctly identified it as FUD. People have a bone to pick with Pin, so they irrationally latch on to it, but the general problem is the fact that the &mut invariants cannot currently permit any self-referential data, which is a useful concept in general (for intrusive data structures, etc) and whose lack that people have been hacking around since before 1.0, with crates like rental and owning_ref. The plan to fix this is to make self-referentiality a first-class concept in the language, as a principled exception to the usual &mut uniqueness invariant that preserves memory safety while properly encoding the aliasing guarantees.
Re:Speed of Rust vs. C by dataangel on Saturday March 13, 2021 @01:27PM (#26448680)
> The plan to fix this is to make self-referentiality a first-class concept in the language, as a principled exception to the usual &mut uniqueness invariant that preserves memory safety while properly encoding the aliasing guarantees.

Are there issues I can subscribe to or RFCs for this?

Re:Speed of Rust vs. C by kibwen on Monday March 15, 2021 @12:00PM (#26467593)
Re:Speed of Rust vs. C by ameliaquining on Saturday March 13, 2021 @12:42PM (#26448228)
Source? I would like this to be true, but I haven't actually seen it anywhere.
Re:Speed of Rust vs. C by steveklabnik on Saturday March 13, 2021 @01:10PM (#26448534)
https://news.ycombinator.com/item?id=26410487 (it's a significant part, though not the entirety, of this comment)
Re:Speed of Rust vs. C by kibwen on Monday March 15, 2021 @11:59AM (#26467580)