diff options
| author | Manish Goregaokar <manishsmail@gmail.com> | 2020-07-20 12:30:14 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-07-20 12:30:14 -0700 |
| commit | 241374a93b4fe45daf2783b78415ba9a7928c790 (patch) | |
| tree | 8b5110c1429374fb736b3220659accfb099e8cb6 /library/std/src/sys/unix/stack_overflow.rs | |
| parent | 105cd4955425de2613ac2ae6c2d2d1baf17ebd2b (diff) | |
| parent | c3756927478afe8d3a880edc469afd766c2f9e82 (diff) | |
| download | rust-241374a93b4fe45daf2783b78415ba9a7928c790.tar.gz rust-241374a93b4fe45daf2783b78415ba9a7928c790.zip | |
Rollup merge of #73197 - c410-f3r:ranges, r=dtolnay
Impl Default for ranges
Couldn't find an issue about it.
`Range` and friends probably can implement `Default` if `Idx: Default`. For example, the following would be possible:
```rust
#[derive(Default)]
struct Foo(core::ops::RangeToInclusive<u64>);
let _ = [1, 2, 3].get(core::ops::Range::default());
core::ops::RangeFrom::<u8>::default().take(20).for_each(|x| { dbg!(x); });
fn stuff<T: Default>() { let instance = T::default(); ... more stuff }
stuff::<core::ops::RangeTo<f32>>();
```
Maybe there are some concerns about safety or misunderstandings?
Diffstat (limited to 'library/std/src/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions