Rust is Memory Safe

I'm saging because I'm hatespamming the klabnik faggot but I don't want to bump the thread to the top. How new are you?

How pathetic is your life?

Very pathetic. I could use a friend, want to join me?

Snake oil programming confirmed. LOL rust nigger btfo.

You forgot D
en.wikipedia.org/wiki/D_(programming_language)

(checking these doubles)
en.wikibooks.org/wiki/D_Programming

D isn't in the same class as it's pretty much unusable without GC and GC is a non-starter for most systems work.

Can someone explain to me what the hell does OP's unreadable Rust code actually do? And why it's a problem? Thanks.

t. a retard who only knows C++98

It has perl-like semantics of functions returning the value of the last statement without an explicit "return", except the whitespace between ; and } is also considered a statement. Does that answer your question?

1: allocate a string
2: free the string
3: use the string
all without the use of unsafe, which means that rusts memory safety guarantee was broken.
fn main() { let foo = "Hello, use after free!".to_string(); match "this doesn't matter" { // _ is a special pattern that matches everything _ if always_false_also_free_the_string(foo) => { unreachable!(); } _ => { println!("the string was freed: {}", foo); } }}fn always_false_also_free_the_string(never_used: String) -> bool { drop(never_used); // frees the string false}