News for hackers. Stuff that matters.
Re:Death to C by wyldfire on Saturday May 02, 2015 @10:08AM (#9477081)
I'll confess, I have looked ever-so-briefly at D and Go and I figured that Rust was probably similar to Go but I just didn't take the time to learn about it. I like the idea of D (especially design-by-contract), but I have difficulty convincing my colleagues (and myself) that a product with a garbage collector can perform consistently well enough.

Then I read this in TFA:

> Despite guaranteeing memory safety, Rust does not have a garbage collector or runtime, and one of the benefits of this is that Rust code can be called from C with no setup at all.

Maybe I should think about it as "you always enable ASan in your production binary"? That suits me just fine, if that's one of its major benefits. I will resolve today to follow up on Rust and try to learn more about it.

Re:Death to C by steveklabnik on Saturday May 02, 2015 @10:12AM (#9477100)
Most of Rust's safety guarantees are at compile time, not at runtime, and so have no runtime overhead. ASan's docs claim a 2x slowdown.

That said, defense in depth is always nice. kmc got AFL working with Rust recently, and it's uncovered some things. Using an ASan-like tool to do some of the runtime stuff would be great to have.

Re:Death to C by wyldfire on Saturday May 02, 2015 @10:19AM (#9477138)
> uncovered some things

Those were problems with the rust compiler or the binaries it generates?

Re:Death to C by steveklabnik on Saturday May 02, 2015 @10:23AM (#9477154)