diff options
| author | bors <bors@rust-lang.org> | 2015-07-17 18:35:50 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2015-07-17 18:35:50 +0000 |
| commit | e05ac3938bcbdd616930bb010a3bbfa35f22850e (patch) | |
| tree | 5dff08da2e93522a4418ecf43bf79ade8e984e87 /src/libstd/sys/unix/stack_overflow.rs | |
| parent | d4432b37378ec55450e06799f5344b4b0f4b94e0 (diff) | |
| parent | de6b3c282e2e400ce114b5553c3f7080a1434a5f (diff) | |
| download | rust-e05ac3938bcbdd616930bb010a3bbfa35f22850e.tar.gz rust-e05ac3938bcbdd616930bb010a3bbfa35f22850e.zip | |
Auto merge of #27045 - nikomatsakis:better-object-defaults-error, r=pnkfelix
Transition to the new object lifetime defaults, replacing the old defaults completely.
r? @pnkfelix
This is a [breaking-change] as specified by [RFC 1156][1156] (though all cases that would break should have been receiving warnings starting in Rust 1.2). Types like `&'a Box<Trait>` (or `&'a Rc<Trait>`, etc) will change from being interpreted as `&'a Box<Trait+'a>` to `&'a Box<Trait+'static>`. To restore the old behavior, write the `+'a` explicitly. For example, the function:
```rust
trait Trait { }
fn foo(x: &Box<Trait>) { ... }
```
would be rewritten as:
```rust
trait Trait { }
fn foo(x: &'a Box<Trait+'a>) { ... }
```
if one wanted to preserve the current typing.
[1156]: https://github.com/rust-lang/rfcs/blob/master/text/1156-adjust-default-object-bounds.md
Diffstat (limited to 'src/libstd/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions
