-
Notifications
You must be signed in to change notification settings - Fork 13.3k
recursive bounds do not work (a.k.a., f-bounded polymorphism) #2355
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
Comments
@nikomatsakis So, obviously your example is using out-dated syntax, but just to be clear: You're talking about bounds on a type-parameter, not on a value-parameter, right? I.e. I would write your example as something like:
|
Also, the trivial form I give above compiles; so I'll try to come up with a real-world use case of f-bounded polymorphism just to double-check that this bug is still a real problem. |
it's very possible that it works now |
Visiting for triage, I agree that this compiles today. It sounds like we're not sure what an example test case of this would be, so I'm going to close for now and this can be re-opened if a test case comes up. Feel free to also reopen if you think there's more to do! |
Needs a test in the suite before it should be closed. |
reassigning to self so that I remember to make a test |
make a test deterministic
This flag makes benchcomp not create a fresh copy of each benchmark directory before running each variant. The default behaviour is to make a new copy each time, to avoid built artefacts from silently being skipped, and to ensure that patches apply cleanly. Users can use this flag when benchmark runs are guaranteed to be idempotent, to avoid waiting for benchmark suites to be copied to a fresh directory.
The following fails:
Weird as it looks there are good use cases for this. We should support it. IIRC, the code almost does it right, or maybe even does it right, if the name resolution were patched up properly.
The text was updated successfully, but these errors were encountered: