News for hackers. Stuff that matters.
Re:Why asynchronous Rust doesn't work by pornel on Sunday November 14, 2021 @03:47PM (#29220500)
mem::forget() is not crashy like free(). It merely prevents destructors from being run (e.g. you could do the same by storing the value in a global variable). It's a safe method, subject to usual safety checks.

You can use an `unsafe {}` block to call literally libc::free(), or dereference a random raw C pointer, or do something else crashy. However, when talking about Rust's safety rules it's usually assumed we're not talking about code bypassing these rules on purpose.

There are no comments on this comment yet.