News for hackers. Stuff that matters.
Re:Explore the ownership system in Rust by lohankin on Monday January 19, 2015 @10:13PM (#8915287)
Noisy, unreadable code, obsessed with ownership, may give rise to whole new classes of errors that otherwise won't be there. Good that someone experimented with building a language around ownership, but for me it all demonstrates that the idea is not viable. I tried to read 10 tutorials already, each leaving me more confused than ever before.
Re:Explore the ownership system in Rust by Animats on Monday January 19, 2015 @11:20PM (#8915468)
I tried to read 10 tutorials already, each leaving me more confused than ever before.

I can understand that. The language has been changing so fast that most of the stuff on the Web is outdated or wrong. I just found a place in the official reference manual that's out of sync with the compiler, and sent in a note. (The lambda/closure syntax is still in a state of flux.)

Rust roughly follows C/C++/Java syntax, except that, like Go, it's a "name: type" language. Talking about ownership in code is new, as is the syntax for that. The ownership syntax is a bolt-on, and it shows. The lambda syntax is kind of weird; the designers went for conciseness over clarity. Some of this will take getting used to. The syntax is no worse than C++, and in some areas, better.

The syntax isn't the hard part, anyway. It's living within the ownership restrictions that's hard. It's hard because that's a design issue. There's a Rust port of Doom, and it has far too much unsafe code, because Doom's data structures were not designed with Rust in mind. It's not yet clear how big an issue this will be. The remark that 10% of Servo, the web page renderer, is unsafe code is a bad sign.

I don't have a personal opinion on this yet. I haven't written enough Rust code. I'm writing an RSS feed parser to get a sense of what it's like to deal with a complex tree in Rust. So far, it's going well, with no need for unsafe code.

If Rust can eliminate buffer overflows, dangling pointers, and memory leaks, that's enough to justify using it in place of C/C++.

Re:Explore the ownership system in Rust by dbaupp on Tuesday January 20, 2015 @02:40AM (#8915858)
Where did the 10% number come from?

FWIW, I just looked at the code in the mozilla/servo repository: more than half (1291) of all mentions of 'unsafe' (2150) are inside autogenerated bindings to CEF (Chromium Embedding Framework), which doesn't seem at all like the interesting/relevant part of the application (it's providing an optional "minimal working" browser chrome for the rendering engine). A lot of the other uses are similarly for other FFI tasks, interfacing with libraries like FreeType, HarfBuzz and Spidermonkey. Obviously it would be nice for those libraries to be in Rust and thus avoid the FFI-is-always-unsafe , but the ecosystem is still young and those libraries are seriously non-trivial, Mozilla and the Servo team presumably want to be able to do the interesting parts of their experimentation rather than spending years porting all the low-level libs to Rust first.

For some "success stories", Servo's CSS parser was now pure Rust, and has a single `unsafe` block: https://github.com/servo/rust-cssparser/blob/38877bc0a50a64a... . Similarly, the pure Rust HTML parser written for Servo doesn't have much unsafe (certainly very little compulsory unsafe, most exists in an alternate DOM implementation, or in the C interface the library exposes): https://github.com/servo/html5ever

That said, Rust is definitely not perfect in this regard, three of the major failings with Rust that force Servo to have a unsafe code are insufficient data-parallel libraries, lack of inheritance-like features to allow the DOM to be CPU and memory efficient, and lack of garbage collection hooks in the compiler.

> The ownership syntax is a bolt-on, and it shows.

Could you go into more detail about what you mean by this?

Re:Explore the ownership system in Rust by wycats on Tuesday January 20, 2015 @12:05AM (#8915560)
For what it's worth, I've written two fairly large pieces of code in Rust: Skylight and much of Cargo. In both cases, the amount of unsafe code was very small (tiny) and restricted to FFI boundaries, which are "unsafe" even in high level languages like Ruby.

Servo has been under active development for far longer, and sometimes used unsafe code to work around historical issues that no longer require unsafe code. I find the idea of an idiomatic codebase (written today), that is 10% unsafe code (outside of FFI boundaries) to be difficult to imagine.

Re:Explore the ownership system in Rust by eddyb on Tuesday January 20, 2015 @01:25AM (#8915706)
Mentioning Go for `name: type` may not be inaccurate, but it is an odd choice (we're seeing more comparisons of Rust and Go than Rust and any language it is closely related to). I believe the origin for Rust's choice is actually the ML family. EDIT: I just checked more carefully and Go doesn't even have the colon ([this blog post](http://blog.golang.org/gos-declaration-syntax) used it in pseudocode).
Re:Explore the ownership system in Rust by Animats on Tuesday January 20, 2015 @01:54AM (#8915759)
Sorry. "name : type" comes from Pascal, and the Modula/Ada/Oberon family of languages continue it. Now that type expressions have become so complex, it's better to have a syntax where you know a type expression is expected. C/C++ struggle with this; they have to know which names are types just to parse. This is a pain for tools which try to parse C/C++ without reading all the include files. C originally had only built-in type names and "struct". "typedef" came later, and made the syntax context-dependent.
Re:Explore the ownership system in Rust by adamnemecek on Monday January 19, 2015 @10:24PM (#8915322)
> obsessed with ownership, may give rise to whole new classes of errors that otherwise won't be there

How does baking the ability to statically determine resource ownership into a language lead to a class of errors? What sort of errors are these?

Re:Explore the ownership system in Rust by lohankin on Monday January 19, 2015 @10:40PM (#8915363)
By taking away the ability of programmer to read and understand the code written by somebody else, or by himself 1 week ago
Re:Explore the ownership system in Rust by wycats on Tuesday January 20, 2015 @12:06AM (#8915565)
As someone who has written many thousands of lines of production Rust code, this doesn't ring true to me at all. Ownership semantics have dramatically improved my ability to reason about my code, not the opposite.
Re:Explore the ownership system in Rust by adamnemecek on Monday January 19, 2015 @10:44PM (#8915379)
I have no clue what you are talking about and I don't think that you have either so I'll just leave this discussion now.
Re:Explore the ownership system in Rust by Retra on Monday January 19, 2015 @10:36PM (#8915353)
Have you written any code?