diff options
| author | bors <bors@rust-lang.org> | 2015-08-27 07:13:02 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2015-08-27 07:13:02 +0000 |
| commit | d6a65cd3fefb238c05cd26414112d5809e940f85 (patch) | |
| tree | b859f705fd8c01db36e71945fc6d4d4fe8cf7ab2 /src/libstd/sys | |
| parent | 0d5142f9b8c5897c4bda662fdcf47a4cb208677e (diff) | |
| parent | 651c42f11f6870dd2c23a1b33fed9ddefd043b76 (diff) | |
| download | rust-d6a65cd3fefb238c05cd26414112d5809e940f85.tar.gz rust-d6a65cd3fefb238c05cd26414112d5809e940f85.zip | |
Auto merge of #27975 - sfackler:iter-order-methods, r=aturon
This does cause some breakage due to deficiencies in resolve - `path::Components` is both an `Iterator` and implements `Eq`, `Ord`, etc. If one calls e.g. `partial_cmp` on a `Components` and passes a `&Components` intending to target the `PartialOrd` impl, the compiler will select the `partial_cmp` from `Iterator` and then error out. I doubt anyone will run into breakage from `Components` specifically, but we should see if there are third party types that will run into issues. `iter::order::equals` wasn't moved to `Iterator` since it's exactly the same as `iter::order::eq` but with an `Eq` instead of `PartialEq` bound, which doensn't seem very useful. I also updated `le`, `gt`, etc to use `partial_cmp` which lets us drop the extra `PartialEq` bound. cc #27737 r? @alexcrichton
Diffstat (limited to 'src/libstd/sys')
0 files changed, 0 insertions, 0 deletions
