diff options
| author | bors <bors@rust-lang.org> | 2016-08-21 15:12:43 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2016-08-21 15:12:43 -0700 |
| commit | 42584d36f6a2d8021c0b642ec0cbf1afed750f32 (patch) | |
| tree | f058fd1eb31f1fcfe507e35e887a917a487cb97c /src/libsyntax/parse/parser.rs | |
| parent | 1576de0ce6b75fd177eca289a2826d0190e407a5 (diff) | |
| parent | c32456da8f14a7c4206278c55b90a535c4d98e20 (diff) | |
| download | rust-42584d36f6a2d8021c0b642ec0cbf1afed750f32.tar.gz rust-42584d36f6a2d8021c0b642ec0cbf1afed750f32.zip | |
Auto merge of #35777 - nrc:carrier3, r=@nikomatsakis
Carrier trait (third attempt) This adds a `Carrier` trait to operate with `?`. The only public implementation is for `Result`, so effectively the trait does not exist, however, it ensures future compatibility for the `?` operator. This is not intended to be used, nor is it intended to be a long-term solution. Although this exact PR has not been through Crater, I do not expect it to be a breaking change based on putting numerous similar PRs though Crater in the past. cc: * [? tracking issue](https://github.com/rust-lang/rust/issues/31436) * [previous PR](https://github.com/rust-lang/rust/pull/35056) * [RFC issue](https://github.com/rust-lang/rfcs/issues/1718) for discussion of long-term Carrier trait solutions. r? @nikomatsakis
Diffstat (limited to 'src/libsyntax/parse/parser.rs')
0 files changed, 0 insertions, 0 deletions