Skip to content

Conversation

@huonw
Copy link
Contributor

@huonw huonw commented Jun 15, 2013

This is caused by StrVector having a generic implementation for &[S]
and so #5898 means that method resolution of [[1]].concat() sees that
both StrVector and VectorVector have methods that (superficially) match.

They are now connect_vec and concat_vec, which means that they can actually be
called.

…h StrVector.

This is caused by StrVector having a generic implementation for &[S]
and so rust-lang#5898 means that method resolution of ~[~[1]].concat() sees that
both StrVector and VectorVector have methods that (superficially) match.

They are now connect_vec and concat_vec, which means that they can actually be
called.
bors added a commit that referenced this pull request Jun 15, 2013
This is caused by StrVector having a generic implementation for &[S]
and so #5898 means that method resolution of ~[~[1]].concat() sees that
both StrVector and VectorVector have methods that (superficially) match.

They are now connect_vec and concat_vec, which means that they can actually be
called.
@bors bors closed this Jun 15, 2013
@bors bors merged commit 1854256 into rust-lang:master Jun 15, 2013
flip1995 pushed a commit to flip1995/rust that referenced this pull request Jun 4, 2022
Add new lint `mismatching_type_param_order`

changelog: Add new lint [`mismatching_type_param_order`] for checking if type parameters are consistent between type definitions and impl blocks.

fixes rust-lang#7147
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.

3 participants