Skip to content

Reject all uses of non-typaram bounds #20688

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed

Conversation

jroesch
Copy link
Member

@jroesch jroesch commented Jan 7, 2015

This is a follow up to my recent PR. r? @nikomatsakis

@jroesch jroesch force-pushed the reject-non-param-bounds-followup branch from 1e03b0a to 120a520 Compare January 7, 2015 19:27
@frewsxcv
Copy link
Member

frewsxcv commented Jan 7, 2015

For reference, here's the other PR @jroesch mentioned: #20623

}
_ => {}
}
}
Copy link
Member

Choose a reason for hiding this comment

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

Shouldn't this have a walk_trait_item call somewhere?

Copy link
Contributor

Choose a reason for hiding this comment

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

Hmm, good point.

@jroesch jroesch force-pushed the reject-non-param-bounds-followup branch from 120a520 to f61e438 Compare January 8, 2015 01:22
@jroesch jroesch force-pushed the reject-non-param-bounds-followup branch from f61e438 to 7eab953 Compare January 8, 2015 01:23
alexcrichton added a commit to alexcrichton/rust that referenced this pull request Jan 8, 2015
@alexcrichton
Copy link
Member

Merged in #20733

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants