Skip to content
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

implements and "Did not expect BoundT" #3243

Closed
alexeygolev opened this issue Jan 22, 2017 · 2 comments
Closed

implements and "Did not expect BoundT" #3243

alexeygolev opened this issue Jan 22, 2017 · 2 comments
Assignees
Labels

Comments

@alexeygolev
Copy link

Here is the tryflow
Not sure if it's a bug or the way I'm using it.
I couldn't find a similar use case in flow tests.

@mroch
Copy link
Contributor

mroch commented Jan 23, 2017

@samwgoldman you're probably the best one to look into this.

looks like it ends up doing an InstanceT ~> ImplementsT where it compares the two map methods, but at least one hasn't been specialized for whatever reason (I think that's the bug?) so it does a PolyT ~> PolyT where the A from the interface hasn't been subst'd.

@mroch mroch added the Crash label Jan 23, 2017
@samwgoldman
Copy link
Member

drat! investigating...

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

No branches or pull requests

4 participants