A longer reply, to give you answers, in case you're still wondering:
(this is in the spirit of letting you know the answers to the questions, not saying that it's not a weakness of the docs.
In general, this is meant to assume that you have knowledge of Rust already. But most of this is going away in the re-organization, so it should be less confusing anyway.
It's just that this causes a data race.
It's true, this is 'deref coercions'. There's a whole section in the new TOC abou tit.
That's a bummer, as it's a major part of this section
str is a primitive type that's not sized.
String is a library type, that's an owned, heap-allocated string.
As the documentation for
graphemes says: http://doc.rust-lang.org/nightly/unicode/str/trait.UnicodeStr.html#tymethod.graphemes .... it doesn't anymore. It used to. You basically always pass true as far as I'm concerned
Empty structs don't need bodies. I basically just left
out of the example, maybe it'd be more clear with it there. I was trying to say that it works for any struct, rather than unit structs only.
I think recent drafts have extra text here, unsure.
That is the blah blah blah. Errors at a distance.
Yeah, this is because numbers are Copy, which are copied on move. Maybe shouldn't use a Copy type.
yeah, this is basically sugar.
The associated type is named
Yeah, I left this in for accuracy, but didn't want to get into calling conventions.
You can use
enumerate() if you also need an index, so this case isn't actually an advantage.
I'll review the copy-editing in this section. They're equivlanet forms.
Because it's not a pointer:
&x pattern matches a pointer, and
x is a value.
Wait, in C++, if a template compiles, it still may not work? that sounds... terrible. This is just me not being familliar with C++ details, and assuming things work as they should
Partial equality as opposed to total equality.
that's a cast, which has its own section in the new TOC
Right, the intention here is to show the underlying structure which the compiler uses.
The problem here is the clash with the builtin types....
all macros can be invoked with
I guess that closures capturing things they referred to was known.
of the top of my head, no idea.
This is called 'shadowing' and is pretty pervasive in Rust code, I'll make sure it's in the bindings section.
Not at all, it's just to show a program that does something.
Yeah, this type got removed RIGHT BEFORE beta, so links break :/ I'll update it.