02: ambiguous statement

[adrientetar]

Any pointer or reference in Rust, be it to an int or a complicated struct will be a pointer to a box.

That's partially wrong; a reference (&) is just pointing to a chunk of memory; which if unboxed will be itself unboxed.

So, for example, &int is not a pointer to a box.

(Side note: it would be cool to have the text compiled from Markdown source or something like it; I use pandoc in my project).

[evansuva]

Thanks, Adrien!

That's a good point - we'll review it.

The tutorial is using a markdown-like language, but a very simple custom
one that Alex and Wil made for this to handle the code examples well
(but not all the things one can do with pandoc). The sources are in
https://github.com/aml3/RustTutorial/tree/gh-pages/html/pre

Cheers,

--- Dave

On 1/22/14, 3:50 PM, Adrien Tétar wrote:

Any pointer or reference in Rust, be it to an |int| or a complicated
|struct| will be a pointer to a box.

That's partially wrong; a reference (|&|) is just pointing to a chunk of
memory; which if unboxed will be itself unboxed.

So, for example, |&int| is not a pointer to a box.

(Side note: it would be cool to have the text compiled to Markdown
source or something like it; I use pandoc in my project
https://github.com/adridu59/rust-tuts).

—
Reply to this email directly or view it on GitHub
#5.

[adrientetar]

Thanks for the answer!
Also, if I may make a practical suggestion, it would be cool to have gh-pages set as the default GitHub branch (I first started looking at outdated master when I came across the repo).

[evansuva]

That's a good idea. Its set up as the default branch now.