3 ms·
There are several inaccuracies here regarding Rust, unfortunately: "Boxes, which can be owned by only one owner, contain the data." We usually use "box" to me
by pcwalton 15y ago
There are several inaccuracies here regarding Rust, unfortunately:
"Boxes, which can be owned by only one owner, contain the data."
We usually use "box" to mean "task-local data", which can't move. (Some of us are trying to drift away from the "box" terminology altogether, since it's potentially confusing -- "GC data" or "task-local data" is easier.) Generally we use the term "uniquely-owned data" for data that's intended to move from task to task.
"This is conceptually similar to mutexes, but with an orderly transfer of control and no option for waiting for a box."
The comparison to mutexes is puzzling; mutexes are for protecting access to shared data, while unique pointers are for transfer of ownership of data with a single owner. In any case, you can wait for uniquely-owned data to arrive on a channel; just use the blocking receive function.
"Right now, it appears to be the product of a single individual."
This is simply untrue. We have about a half-dozen core Rust developers in Research and several community contributors. Most of us have other responsibilities, but Rust is one of the top priorities of the research team as a group. The commit logs [1] reflect this.
[1]: https://github.com/mozilla/rust/commits/master https://github.com/mozilla/rust/commits/master
- kibwen 15y agoRe: Rust contributors, Github's new graphs make the case quite well: https://github.com/mozilla/rust/graphs/contributors https://github.com/mozilla/rust/graphs/contributors