[rust-dev] Work week minutes and upcoming RFCs
glaebhoerl at gmail.com
Fri Mar 14 12:26:56 PDT 2014
"Disallow taking the address of a non-mut static value unless it is Freeze"
Can someone explain why this is necessary?
static FOO: Option<Cell<int>> = None;
let foo = &FOO;
Why would this be a problem? Or is this not what's being referred to?
Actually... given that you can't move out of a static, and all
functions/methods are either by value (moves) or by ref (takes address),
this means the only way you could interact with a non-Freeze static _at
all_ is if it were Pod/Copy. But Pod/Copy types are never non-Freeze. So...
On Mon, Mar 10, 2014 at 4:27 AM, Brian Anderson <banderson at mozilla.com>wrote:
> Last week a number of us got together to hash out designs for the
> remaining features in Rust 1.0, with the goal of producing RFC's for each
> in the upcoming weeks.
> I'm very optimistic about how it's all going to come together, and that
> the quantity of work to be completed is reasonable.
> I've put the minutes for the week up on the wiki for the curious, but I
> warn you that they are sometimes inscrutable.
> : https://github.com/mozilla/rust/wiki/Meeting-workweek-2014-03-03
> As I mentioned, folks will be writing RFC's on all the major topics to get
> feedback, and they are going to do so according to a tweaked RFC process
> aimed at introducing new features into Rust in a more controlled way than
> we have in the past. More about that later.
> Rust-dev mailing list
> Rust-dev at mozilla.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Rust-dev