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

TypeAnalyzer infinite loop #348

Closed
danrubel opened this issue Nov 4, 2011 · 4 comments
Closed

TypeAnalyzer infinite loop #348

danrubel opened this issue Nov 4, 2011 · 4 comments
Assignees
Labels
P1 A high priority bug; for example, a single project is unusable or has many test failures

Comments

@danrubel
Copy link

danrubel commented Nov 4, 2011

Given the cyclic definition below, the TypeAnalyzer$Analyzer$AbstractMethodFinder.visitClass(DartClass) never returns.

class Foo extends Bar {
}

class Bar extends Foo {
}

@DartBot
Copy link

DartBot commented Nov 7, 2011

This comment was originally written by mmendez@google.com


Removed Priority-Medium label.
Added Priority-High label.

@scheglov
Copy link
Contributor

scheglov commented Nov 7, 2011

Set owner to @scheglov.
Added Accepted label.

@scheglov
Copy link
Contributor

scheglov commented Nov 7, 2011

Added Started label.

@scheglov
Copy link
Contributor

scheglov commented Nov 7, 2011

Fixed in trunk.
Now we will not continue identifying unimplemented methods, if there is cyclic declaration.


Added Fixed label.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 A high priority bug; for example, a single project is unusable or has many test failures
Projects
None yet
Development

No branches or pull requests

3 participants