On 4/10/14 10:17 PM, comex wrote:
On Thu, Apr 10, 2014 at 2:28 PM, Alex Crichton <[email protected]> wrote:
[1] -
https://github.com/rust-lang/rfcs/blob/master/active/0003-opt-in-builtin-traits.md
Off topic, but sigh... first private fields, now this to add even more
verbosity to declaring a struct, which really should be a very low
friction thing. Not the end of the world but I don't like it.
The API stability problem and the inability for us to add more bounds
later are real issues though.
(Not to mention the fact that I've spent a lot of time in Servo hunting
down the one field that caused a big complex structure not to become
`Send`. I've also had issues whereby commits in a large project sneak in
that make structures that I wanted to remain sendable suddenly become
not sendable, requiring awkward useless "assertion" functions that
ensure that it doesn't happen in the future. These are potentially
fixable in other ways, but it just seems cleaner to require structures
opt in to the built-in traits.)
Patrick
_______________________________________________
Rust-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/rust-dev
