3 ms·
From the presentation introducing Rust to Mozilla: http://venge.net/graydon/talks/intro-talk-2.pdf http://venge.net/graydon/talks/intro-talk-2.pdf > I have bee
by steveklabnik 3y ago
From the presentation introducing Rust to Mozilla: http://venge.net/graydon/talks/intro-talk-2.pdf http://venge.net/graydon/talks/intro-talk-2.pdf
> I have been writing a compiled, concurrent, safe, systems programming language for the past four and a half years.
Safety was always part of it.
- cmrdporcupine 3y agoBut those "Safety" definitions are all not like what Rust folks mean by safety now. He's talking about immutability and bounds checking and avoiding memory corruption but not at all about borrowing. I guess I should have been more specific. If that's what we mean by safe, then OCaml is safe as well. Anyways, I followed it at the time. The borrow checker came later.
- deleted 3y ago[deleted]
- steveklabnik 3y agoI absolutely agree the borrow checker came later. I think of it as that the goals have always been the same, but the enforcement mechanism changed over time, as more and more static ways were found to achieve the goal.
- deleted 3y ago[deleted]