-
Notifications
You must be signed in to change notification settings - Fork 12.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use assoc types in the *Iterator traits #20441
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Other than a couple of possible mergers, this LGTM! |
Is |
@bluss #![crate_type = "lib"]
#![feature(associated_types)]
trait Iterator {
type Item;
fn ok() -> Self::Item;
}
trait DoubleEndedIterator: Iterator {
fn doesnt_work() -> Self::Item;
fn works() -> <Self as Iterator>::Item;
} Unless @nikomatsakis fixed it while I was sleeping ;-). |
💛 |
bors
added a commit
that referenced
this pull request
Jan 4, 2015
closes #20486 closes #20474 closes #20441 [breaking-change] The `Index[Mut]` traits now have one less input parameter, as the return type of the indexing operation is an associated type. This breaks all existing implementations. --- binop traits (`Add`, `Sub`, etc) now have an associated type for their return type. Also, the RHS input parameter now defaults to `Self` (except for the `Shl` and `Shr` traits). For example, the `Add` trait now looks like this: ``` rust trait Add<Rhs=Self> { type Output; fn add(self, Rhs) -> Self::Output; } ``` The `Neg` and `Not` traits now also have an associated type for their return type. This breaks all existing implementations of these traits. --- Affected traits: - `Iterator { type Item }` - `IteratorExt` no input/output types, uses `<Self as Iterator>::Item` in its methods - `DoubleEndedIterator` no input/output types, uses `<Self as Iterator>::Item` in its methods - `DoubleEndedIteratorExt` no input/output types, uses `<Self as Iterator>::Item` in its methods - `RandomAccessIterator` no input/output types - `ExactSizeIterator` no input/output types, uses `<Self as Iterator>::Item` in its methods This breaks all the implementations of these traits.
kui
added a commit
to kui/racer
that referenced
this pull request
Jan 5, 2015
This error is the following: ``` $ make rustc -O -o bin/racer src/main.rs src/racer/codeiter.rs:22:10: 22:32 error: wrong number of type arguments: expected 0, found 1 src/racer/codeiter.rs:22 impl<'a> Iterator<(uint, uint)> for StmtIndicesIter<'a> { ^~~~~~~~~~~~~~~~~~~~~~ ``` This is caused by rust-lang/rust#20441
kui
added a commit
to kui/racer
that referenced
this pull request
Jan 5, 2015
This error is the following: ``` $ make rustc -O -o bin/racer src/main.rs src/racer/codeiter.rs:22:10: 22:32 error: wrong number of type arguments: expected 0, found 1 src/racer/codeiter.rs:22 impl<'a> Iterator<(uint, uint)> for StmtIndicesIter<'a> { ^~~~~~~~~~~~~~~~~~~~~~ ``` This is caused by <rust-lang/rust#20441>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Affected traits:
Iterator { type Item }
IteratorExt
no input/output types, uses<Self as Iterator>::Item
in its methodsDoubleEndedIterator
no input/output types, uses<Self as Iterator>::Item
in its methodsDoubleEndedIteratorExt
no input/output types, uses<Self as Iterator>::Item
in its methodsRandomAccessIterator
no input/output typesExactSizeIterator
no input/output types, uses<Self as Iterator>::Item
in its methodsThis breaks all the implementations of these traits.
[breaking-change]
I was planning to use assoc types in the
AdditiveIterator
trait but that can't be done until this bug (#20400) is fixed.r? @aturon