-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
F bounded quantification bug #25530
Comments
I believe this is the issue I'm hitting now. I've spent the last day or so moving projects to strong mode, adding generic method parameters and getting rid of analyser warnings. But when I go to run the unit tests pretty much everything blows up now like
Looking at the classes referenced here I believe the analyser is correct and the problem is at runtime.
Any suggestions on a workaround? This is breaking things for me now |
Do you have a self contained set of classes that exhibit the problem? What did the original code look like? |
I'll work on a repro. I might wait till #25568 is fixed on the odd chance that it is in some way related as it relates to similar classes |
This version doesn't have any strong mode errors in the latest build: class Entities<T extends ConceptEntity<T>> implements EntitiesApi<T> { }
class ConceptEntity<T extends ConceptEntity<T>> implements EntityApi<T> { }
abstract class EntityApi<T extends EntityApi<T>> { }
abstract class EntitiesApi<T extends EntityApi<T>> { }
class Concept extends ConceptEntity<Concept> { }
main() {
new ConceptEntity<Concept>();
} ... so it may be possible to use this now. |
thanks to @zoechi for pointing this out :) |
this test is no longer marked failing. |
from @vsmenon, moved from dart-archive/dev_compiler#357
From f_bounded_quantification2_test.dart:
is triggering the following errors - newly in the task model strong mode:
This particular test isn't strictly blocking - we don't support this pattern yet in codegen, but it is a regression.
The text was updated successfully, but these errors were encountered: