Slash Boxes

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 16 submissions in the queue.
posted by takyon on Friday May 15 2015, @10:30PM   Printer-friendly
from the already-rusty dept.

After many years of waiting, version 1.0 of the Rust programming language has finally been released. The Rust home page describes Rust as "a systems programming language that runs blazingly fast, prevents nearly all segfaults, and guarantees thread safety."

Thanks to the hard work of noted Rust core team members Yehuda Katz and Steve Klabnik, Rust is now poised to become a serious competitor to established systems programming languages like C and C++.

The announcement has brought much jubilation to the followers of Rust, who have been eagerly awaiting this milestone release for so long. With only 1,940 open issues and over 11,500 issues already closed, Rust is finally ready for users to build fantastically reliable software systems using it.

This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 3, Funny) by Marand on Saturday May 16 2015, @09:06AM

    by Marand (1081) on Saturday May 16 2015, @09:06AM (#183697) Journal

    There's also Debian's benchmark game [], for whatever it's worth. Definitely slower than C/C++, but like you said it's somewhere in the Go/Haskell/Java (and other JVM languages) area. The trade-off might be worth it for the safety if it proves itself to actually be safer, though in that speed range there's already plenty of competition with similar goals but different approaches.

    Damn shame about the syntax, though. Out of curiosity I started looking at some of the Rust files in the only big project I know of using it, Servo ( [] ), and I swear, there are lines in it that make Perl look readable. I liked this function declaration:

    pub fn match_ty_unwrap<'a>(ty: &'a Ty, segments: &[&str]) -> Option<&'a [P<Ty>]> {

    I'm sure it makes sense to someone familiar with the language, but my general impression so far from poking around random Servo files is "the readability of Perl meets the conciseness of Java." What's not to love?

    Starting Score:    1  point
    Moderation   +1  
       Funny=1, Total=1
    Extra 'Funny' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   3  
  • (Score: 2) by TGV on Saturday May 16 2015, @09:37AM

    by TGV (2838) on Saturday May 16 2015, @09:37AM (#183708)

    Declaration syntax is sure ugly, but I sort of get it: it's pretty much C++/Java but with colons. The passing of &mut everywhere. I don't understand why it can't get that information from the function declaration. Is it also legal to call the same function without &mut, and with a different effect? There is something in that language that isn't explained properly in all those examples and FAQs.

    • (Score: 0) by Anonymous Coward on Saturday May 16 2015, @01:06PM

      by Anonymous Coward on Saturday May 16 2015, @01:06PM (#183743)

      Why did they use the keyword "mut"? It makes me think of a dirty dog pissing all over the place because its penis is broken from having spent years on the street.