Denis (cc'ing rust-dev)-
How does it then interpret the line:
let it = self.items[0];
The only way to make sense of that is to copy, isn't it? What else?
An assignment expression can denote either a copy or a *move* of the
right-hand-side into the left-hand-side.
Note that your goal
Kevin (cc'ing rust-dev)-
Of the choices listed here, I prefer the C++11 syntax.
Whatever syntax we choose, I would prefer one that has user-selected delimiting
character sequences (as illustrated by the cases of D and C++11). From my
point-of-view, that is the only way to get a raw string
Thad (cc'ing rust-dev)-
How will Rust deal with the mutator (the part that modifies user code and
mutates it ) ? From a high level, will it be run as separate computation
threads or within the same computation thread ?
The current goal is for the mutator and GC to be coroutines on the same
Niko (cc'ing Patrick and rust-dev; resending from correct account)-
* Objects in the borrowed set are scanned during each minor
collection, even if they're tenured.
I wouldn't add a non-tenured object to the borrowed set. What's the
point.
What if (1.) the borrowed-object is in the
Niko (cc'ing rust-dev)-
I know about (1), and I can appreciate (2).
I had dismissed (1) because it did not seem like a huge burden to add the extra
line binding `s = some_func_call()` immediately preceding `match s { ... }`;
that's why I classified this case as not-particularly useful.
Artella (cc'ing rust-dev)-
It is an interesting phenomenon that you note.
I think it is arising from the fact that you have *two* expressions of the form
io::println(float::to_str(...)) in the main fn from firstAndSecond.rs, while
each of the other two rs files have only one expression of the
