The Road to Rust 1.0
blog.rust-lang.org
The Road to Rust 1.0
1–10 of 248 posts
Re: The Road to Rust 1.0
#2Adopting the channels system is interesting. Are there any other languages that have a scheduled release pattern like this?
Re: The Road to Rust 1.0
#3> The key to all these changes has been a focus on the core concepts of ownership and borrowing. Initially, we introduced ownership as a means of transferring data safely and efficiently between tasks, but over time we have realized that the same mechanism allows us to move all sorts of things out of the language and into libraries. The resulting design is not only simpler to learn, but it is also much “closer to the metal” than we ever thought possible before. All Rust language constructs have a very direct mapping to machine operations, and Rust has no required runtime or external dependencies.
Almost sounds like they borrowed this thinking from Exokernel design... I think Rust is shaping up to be a very exciting language.
Re: The Road to Rust 1.0
#4Adopting the channels system is interesting. Are there any other languages that have a scheduled release pattern like this?
I'm not aware of any, but if there are, I'd like to talk to them about their experiences doing so. :)
Re: The Road to Rust 1.0
#5It'd be wonderful if they kept the ability to define that a certain destructor does zero memory.
Sometimes, you need that.
Re: The Road to Rust 1.0
#6It'd be wonderful if they kept the ability to define that a certain destructor does zero memory. Sometimes, you need that.
Zeroing out memory isn't sufficient, as discussed here: http://www.daemonology.net/blog/2014-09-06-zeroing-buffers-i...
That said, this was discussed on reddit[0], it sounds like there is a way to guarantee that you did zero out memory (but not necessarily copies of that memory, as discussed in the link above), and because Rust is intended to be memory safe, it's not as much of an issue if you don't/can't.
http://www.reddit.com/r/rust/comments/2fnb82/zeroing_buffers...
Re: The Road to Rust 1.0
#7The ownership idioms are very similar to idiomatic C++11 and std::unique_ptr. Which is to say that Rush has got an industrial strength safe memory management system.
But Rust stands out because the rest of the language is such a joy to use, compared to pretty much any other 'systems' language out there.
Congratulations to the team!
Re: The Road to Rust 1.0
#8I used to describe my preferred family of languages as:
- C when I absolutely had to (kernel/modules/plumbing).
- Python for scripting and broad accessibility.
- Haskell when I had the choice and I knew everybody who would work on the project.
I was skeptical of Rust when it first came out, due in large part to the many different kinds of pointers it originally had, many of which involved significant manual memory management. But now, with a strong static type system, garbage collection, pattern matching, associated types, and many other features, Rust is looking like a serious contender to replace all three of those languages for me.
Still waiting to see if it develops a strong following, community, and batteries-included library ecosystem, but I need to start doing more experiments with Rust.
Disappointing to see yet another language-specific package management system (Cargo), though.
Re: The Road to Rust 1.0
#9I used to describe my preferred family of languages as: - C when I absolutely had to (kernel/modules/plumbing). - Python for scripting and broad accessibility. - Haskell when I had the choice and I knew everybody who would work on the project. I was skeptical of Rust when it first came out, due in large part to the many different kinds of pointers it originally had, many of which involved significant manual memory ma…
Rust does not have any garbage collection, to be clear. All your other features are correct though :)
(We have previously said "opt-in GC" but that was a lie. See https://news.ycombinator.com/item?id=8312327 for more.)
Re: The Road to Rust 1.0
#10I used to describe my preferred family of languages as: - C when I absolutely had to (kernel/modules/plumbing). - Python for scripting and broad accessibility. - Haskell when I had the choice and I knew everybody who would work on the project. I was skeptical of Rust when it first came out, due in large part to the many different kinds of pointers it originally had, many of which involved significant manual memory ma…
Rust does not have any garbage collection, to be clear. All your other features are correct though :) (We have previously said "opt-in GC" but that was a lie. See https://news.ycombinator.com/item?id=8312327 for more.)
Yeah, I should have said that more clearly. Automatic memory management (never having to call free), not garbage collection. Which is arguably more awesome: whenever the compiler can figure out at compile time when you'll stop using memory, it can statically decide to reclaim it there.