News for hackers. Stuff that matters.
Re:Pointers in Rust: a guide by steveklabnik on Friday October 18, 2013 @11:00AM (#6571721)
> I wish you hadn't mentioned managed pointers at all

I originally wrote this as an official guide, so I needed to talk about them, and then I got lazy, and just posted it after the PR got closed. But yes, discouragement is the right approach.

> We need more articles like this to combat the "oh rust is so complicated it has 200 DIFFERENT TYPES OF POINTERS" propaganda.

Exactly. The problem is that pointers are one of the more neat features of Rust, and most people who are new to programming languages like unique[1] features, so it got talked about a lot, so people assumed you needed to know about all these details, when that's not actually true.

I know we all over-used `~str` for a long time...

1: ;)

Re:Pointers in Rust: a guide by kibwen on Friday October 18, 2013 @11:09AM (#6571780)
~str used to be the only string type we had! And vectors were all on the heap and dynamically-sized!!

Kids these days, with your fixed-size arrays and your static strings and your global variables and your hoity-toity region analyses.

Re:Pointers in Rust: a guide by cpeterso on Saturday October 19, 2013 @03:10AM (#6575637)
I'm not sure why people think Rust pointers are so confusing. Any C++ developer familiar with shared_ptr and unique_ptr should understood Rust pointers almost immediately.

The area of Rust that I find most confusing (and sends me back to the documentation and example code every time) is the module system and the relationship between library crates, modules, files, and identifier paths. :\