Nowhere in my comment did I mention C, Firefox, learning curves or marketing so I'm unsure what you're replying to. To be clear, this issue isn't about Rust, t

Nowhere in my comment did I mention C, Firefox, learning curves or marketing so I'm unsure what you're replying to. To be clear, this issue isn't about Rust, the language. This is about Rust's standard library creating a safe abstraction around platform functions (although altering `memcmp` et al would affect how certain language features are implemented). And it doesn't matter what language malloc is written in. It could be Python, C, Rust or brainfuck, the issue is the same. Rust's standard library assumes it is implemented to spec. I'm not sure that it could or should do otherwise.