Viewing profile — withoutboats

This touches on some interesting history: lifetimes were originally (in other PL literature) called "regions" (MS Research's Verona also uses this terminology). Lifetime was chosen…

This is sort of the problem: its very natural to refer to that as a lifetime! In fact, more natural than the lifetime of a reference, because we intuitively think of variables as b…

Your post suggests a bit of confusion about the meaning of "lifetime" in Rust - a confusion which is common and why we are somewhat unhappy with how that terminology has played out…

I don't want to be defensive but this is completely off base, and very disheartening to see you post. Allowing users to write safe self-referential code was never a design goal of …

This situation is the sad and absurd result of two processes going on in the Rust community. The first is that the Rust community on Reddit is in a feedback loop of groupthink and …

There's miles between understanding pinning well enough to call `Box::pin` (a safe API) and understanding pinning well enough to call `Pin::get_mut_unchecked` (an unsafe API). When…

There is a huge gradient of use cases between "high level web frameworks" and "writing everything from scratch" and we've thought about the impact on users at every step of that gr…

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 …

The name for that reference type is a shared reference. It's literally the default reference type. It's not a sufficient guarantee for the use cases Pin supports.

This is exactly the kind of comment that makes me dislike Hacker News so strongly, because I find it endemic here. The idea that someone could think an issue is theoretical and the…

(and the idea I was expressing was "shared references never under any circumstance implement the DerefMut trait")

No one has ever proposed a solution - first class or not - which wouldn't be significantly more invasive and infectious. Does it sound fun in code that doesn't have anything to do …

This was certainly not our intention, or what I've heard from users.

(I was the primary designer of the Pin API.) Since (to a first approximation) every individual who has the expertise and contextual knowledge to really evaluate this issue is a pos…

Thankyou.

Mods: This user's posting history makes clear they are an anti-Semitic conspiracy theorist. Why have you not banned them? https://news.ycombinator.com/item?id=20972062 https://news…

I won't be doing that.

You seem like a really unpleasant person and it doesn't really seem worth my time to interact with you, but I want to point out that your post actually contains no relevant informa…

It's pretty obvious that this person has essentially lied: they have not implemented the complex features they claim while they hype benefits like compile time and lack of non-zero…

The user is the programmer in this context, the user of the programming language, not the end user of the program.

This is the sort of comment on hacker news I absolutely love: I know one of us is sitting in a place of ignorant hubris, and I doubt its me. The problems I refer to are, as I state…

The difference between &str and String is one of my least favorite parts of Rust, but I made your code compile with some pretty trivial changes: https://play.rust-lang.org/?gist=66…

This is the sort of really impressively shallow and baseless analysis that makes Hacker News so enjoyable to read. These two blog posts have really nothing to do with one another, …

It's C. I assume the programmer would just be responsible for dealing with dangling pointers and double frees.