On Tue, Nov 19, 2013 at 6:45 AM, spir <denis.s...@gmail.com> wrote:> > > This helped me too, even if I'm not a C++ programmer (can only read). > However, it is still not enough to understand the meaning of each of those > pointer varieties, imo (at least, _i_ still don't get it). What semantic > kinds of pointed data should go to each variety? why? I would help at once > improving the tutorial if I did understand. > > @Daniel: I would answer your questions if I did understand the *logic* of > Rust's pointers and memory management. The tutorial, in my view, should > precisely help on this. Instead, it tells us about machine-side issues > without meaning (which are important and we need to know, but don't help in > understanding). What is the semantic counter-part of all this? Why does it > exist? > > The logic here is hidden or difficult. As a comparison, we don't need tons > of explanations to understand the differences between a sequential > collection (array, list) and, say, a set. The logic is nearly obvious, we > easily get why both kinds exist. And in fact, the machine-side, > implementation counterpart, while important, comes after, once we understand > the meaning; then we get to know the price one has to pay for quick, direct > access of given items, as opposed to access by index. > > Denis
So in your opinion, what's wrong with the `Boxes` section? http://static.rust-lang.org/doc/master/tutorial.html#boxes I happen to think it does a pretty good job of explaining why `~` is required for recursive types, which is almost the only use case for it from a purely semantic perspective (not worrying about performance). _______________________________________________ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
