DrMeepster

there's a wrapper type, AssertUnwindSafe to get around it. The whole concept of unwind safety was a mistake so don't worry about using it

please no. that article is nonsense. this is all nonsense.

Unsafe is one of the most important things in rust. The point is that you stick all the unsafety into well marked areas that can be more easily checked.

You don't actually explain why Mojo doesn't need Pin, you just say that it works. Does Mojo automatically fix up self referential pointers on moves or something?

See also https://doc.rust-lang.org/nightly/nomicon/leaking.html

Banning unsafe is actually really easy. Just one line `#![forbid(unsafe_code)]` at the start of your code.

Box operator isn't actually used in Box::new anymore. It's been replaced with a magic attribute, #[rustc_box]

Rust also tests all public rust code on github

So to be clear, you want it to be harder to update the compiler? I cannot interpret "rustup seems to encourage that behavior" as anything else but that.

"pronoun people"

What, you cant handle queer people existing?

what does this mean? It sounds like you tried to make a funny programming insult, but it fell flat if that's what you were going for

This can never happen with regular string literals. String literals have the type `&'static str` but formatting returns a `String`.

this study is extremely flawed. It is impossible to tell if these results are from the garbage collection or how bronze violates rust aliasing

ok sure whatever but what does this have to do with the article?

that doesn't mean abuse isn't an asshole move

Would be a lot less work if he didn't do this package splitting nonsense

You can interpret its MIR (mid-level intermediate representation) like Miri or const evaluation does

or maybe it's because most people are not using tor browser and do not vote for links they can't open

RIP mutable noalias (again)

What is a custom lifetime?