News for hackers. Stuff that matters.
Re:C++ design goals in the context of Rust (2010) by pcwalton on Saturday June 21, 2014 @11:26AM (#7925203)
> Rust OTOH seems to have a metric boatload of operators that work in different ways depending on the specific context.

What operators does Rust have that Go does not? I believe Rust has no more operators than Go.

Re:C++ design goals in the context of Rust (2010) by robert_tweed on Saturday June 21, 2014 @12:46PM (#7925414)
This is just my impression based on those tutorials I've looked at so far; I've decided to put off learning it properly until 1.0, whereas I know Go pretty well. IIRC, the move semantics and lifetime annotations were one area that stuck out as pretty heavy on context-specific operators.
Re:C++ design goals in the context of Rust (2010) by Jweb_Guru on Saturday June 21, 2014 @01:37PM (#7925549)
If anything Rust has been busy removing operators. As far as I can recall, move semantics have no operators at all (someone who remembers better can probably correct me on this), and lifetime annotations are just 'lifetime (I suppose you could consider ' an operator?). Rust is also LL(1), so it was a very explicit design decision to have as few context-specific operators as possible (indeed, a few suggestions for possibly more intuitive syntax have been decided against for this reason). So what you're saying really hasn't been my experience with Rust at all. In fact, the only really hard thing about Rust, from my perspective, is the semantics, not the syntax :)
Re:C++ design goals in the context of Rust (2010) by robert_tweed on Saturday June 21, 2014 @02:02PM (#7925601)
Exactly why I'm reserving judgement for now.
Re:C++ design goals in the context of Rust (2010) by pcwalton on Saturday June 21, 2014 @01:31PM (#7925536)
Move semantics don't have operators; they happen automatically invisible. Lifetime annotations are not part of operators; they're part of types. The only operator is the same as in Go, &.