diff options
| author | bors <bors@rust-lang.org> | 2013-06-16 01:52:09 -0700 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2013-06-16 01:52:09 -0700 |
| commit | 08c1155a223eb79960e7a5dbb0ea6276ef9754ea (patch) | |
| tree | fdbb9cbe16c75d9cb615fc651a3946fb6391ed17 /src/rt/rust_task.cpp | |
| parent | d1927d295013e19e57a9773c37ded698e89392eb (diff) | |
| parent | 893c70d7bc670054ef646b71d4d503298cc50d76 (diff) | |
| download | rust-08c1155a223eb79960e7a5dbb0ea6276ef9754ea.tar.gz rust-08c1155a223eb79960e7a5dbb0ea6276ef9754ea.zip | |
auto merge of #7142 : alexcrichton/rust/deriving-zero, r=pcwalton
This allows mass-initialization of large structs without having to specify all the fields. I'm a bit hesitant, but I wanted to get this out there. I don't really like using the `Zero` trait, because it doesn't really make sense for a type like `HashMap` to use `Zero` as the 'blank allocation' trait. In theory there'd be a new trait, but then that's adding cruft to the language which may not necessarily need to be there. I do think that this can be useful, but I only implemented `Zero` on the basic types where I thought it made sense, so it may not be all that usable yet. (opinions?)
Diffstat (limited to 'src/rt/rust_task.cpp')
0 files changed, 0 insertions, 0 deletions
