Just a couple detail responses:
> - Overall: technically strong proposal, but I'm lukewarm about doing it,
> and definitely don't want to *now*. In order, I'd prefer to finish
> what we've got scoped for the next while, then explore Niko's
> sketch, then get to this if we find it necessary.
I agree, and I think Patrick does too.
> - If priv {} is class-private, I think this means adding global state to
> rust? I'm not sure, but that's what I think 'class private' (vs.
> 'instance private') means. If so I'd prefer to rethink that.
No global state; by "class-private" it simply means that all instances of the
same class can see each other's private fields. They're still instance fields.
Dave
_______________________________________________
Rust-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/rust-dev
