Viewing profile — Ygg2

Vantablack pattern?

I'd say unwrap isn't a subtle case either. Yet people see examples and think - "This is the way!"

Keep in mind it's UB to be: > Executing code compiled with target features that the current thread of execution does not support I.e. calling AVX512 on Neon architecture. You need …

Seeing how people were interested about immobile types. Why not discuss the silent MVP of the goals. Rust comptime.

> # How does this relate to the "pin ergonomics" initiative? > This work is an alternative to Project Goal 2025H2: Continue Experimentation with Pin Ergonomics, which includes the …

Pretty sure they ditched that motto long time ago.

I wonder if in a few years, there'll be heads of Google paraphrasing the old skit "You know, in hindsight, allowing autonomous AI drones to carry fusion bombs was a bad move, but f…

Sure, but C code is way older so most of the bugs there should have been excised by now...

Some is doing heavy misrepresentation. Latest batch of LLM's Linux had 423 vulnerabilities. Out of which 10 were Rust*. Would you prefer more or less CVEs? But it's like seat belt …

With Fil-C and Rust the memory safety shouldn't even be discussed. It should be the bare minimum. Presence of worse bugs won't make memory bugs disappear.

> You're just splitting hairs and trying to weasel around the fact No. I said borrow checker allows unbound lifetime. I didn't disagree with you. I noted you didn't read the argume…

> Proof: You just listed examples of unbounded lifetimes. > I said "effectively disable". For example: Not sure what you meant by this example since it doesn't compile. It seems th…

Andreas Kling talked about it. It boils down to C++ interop sucks (no surprise for lang made by Apple), ecosystem is tiny, Rust works well enough with LLMs. https://youtu.be/DbHjKi…

Mu. Invalid question. Rust doesn't disable compiler features. It gives you extra set of footguns when you ask for it. As for the actual unloaded question, "What's the point of unsa…

If you saw the "Institute for Typesafe Memetic Research" and thought, "This is the den of Rust evangelists!" I don't want to break your illusion, because it's much funnier this way…

> Calling him "smelley"? Turnabout is fair play. > Frankly, that entire "Institute for Type Safe Memetic Research" seems like either an elaborate satire or an account run by genuin…

> True, but unsafe let's you conjure up any lifetime you want The only thing unsafe does is let you have an unbounded lifetime. As I said, it doesn't check those: fn get_str (s: *c…

You didn't just quote The Institute of Typesafe Memetic Research as proof of anything... It's a shitposting, hyperbolic bait account. As funny as calling Andrew Kelley Smelley, it'…

Unsafe Rust doesn't automagically disable typesystem (& borrow checker, but lifetime are a sort of types). Once raw pointer is turned into a T, &T or &mut T, the borrow checker is …

> Developer & time-cost of a rewrite is a big unknown... An optimist might say this cost has vanished. I wouldn't say it vanished. I'd say it moved from unknown to known. It's high…

> By the engineer's wit of course! Seeing how the Rust compiler isn't an LLM, it can't really work on wit. From the POV of a programmer, how would you implement an unsafe block? Wh…

Ok, and how does, in your opinion, compiler rules enforcement work in an unsafe block? And how does Miri help solve this issue?

No. I just think you're taking judge by number of segfaults out of context. That said, I wrote this before the edit.