Skip to content

Implement type parameters in the middle of paths #8528

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

Closed
wants to merge 8 commits into from

Conversation

pcwalton
Copy link
Contributor

@nikomatsakis
Copy link
Contributor

Exciting. I have been reading, might take a bit, I'd like to understand what's going on. Though I will try to be fast since I know this will bitrot quickly.

@nikomatsakis
Copy link
Contributor

ok, I am generally r+ on this change, it seems like it's a good first step and the code looked right, though I suspect more changes will be required later (to properly connect type parameters from each point in the path?). I didn't deeply read into what happened with static fns, which seems like a key part, I will try to get to that tonight, but given the bit-rotty nature of this, I don't want to hold things up.

They are still present as part of the borrow check.
For example, `foo::<T>::bar::<U>`.

This doesn't enforce that the type parameters are in the right
positions, however.
…aths.

This removes the stacking of type parameters that occurs when invoking
trait methods, and fixes all places in the standard library that were
relying on it. It is somewhat awkward in places; I think we'll probably
want something like the `Foo::<for T>::new()` syntax.
@pcwalton pcwalton closed this Aug 28, 2013
@pcwalton pcwalton deleted the ty-param-positions branch August 28, 2013 05:19
flip1995 pushed a commit to flip1995/rust that referenced this pull request Jan 9, 2025
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