Skip to content

Support Sized bounds for associated types #18506

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

Merged
merged 5 commits into from
Nov 4, 2014

Conversation

nikomatsakis
Copy link
Contributor

This also refactors associated types in various ways, most notably by moving the associated types defined in a trait into their own param space which replaces the associated-types hashmap (which is just removed). We should probably move the synthetic type parameters into yet another namespace, but that can wait.

Fixes #17921

@nikomatsakis
Copy link
Contributor Author

r? @pcwalton

i += 1;
on_left
});
pub fn split(self) -> (Vec<T>, Vec<T>, Vec<T>, Vec<T>) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we make this return a struct instead?

@pcwalton
Copy link
Contributor

pcwalton commented Nov 3, 2014

r=me with that one fixed

alexcrichton added a commit to alexcrichton/rust that referenced this pull request Nov 4, 2014
@bors bors merged commit 3c84e31 into rust-lang:master Nov 4, 2014
@nikomatsakis nikomatsakis deleted the assoc-type-bounds branch March 30, 2016 16:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support builtin bounds on associated types and make them Sized by default
3 participants