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

hanging while trying to run Dart tests #9

Closed
kevmoo opened this issue May 1, 2013 · 4 comments
Closed

hanging while trying to run Dart tests #9

kevmoo opened this issue May 1, 2013 · 4 comments

Comments

@kevmoo
Copy link
Contributor

kevmoo commented May 1, 2013

dart --checked test/dart_test.dart

Curious if you're seeing this.

I'm on the latest integration build 0.5.1.0 r22072

@renggli
Copy link
Member

renggli commented May 1, 2013

Yeah, I've seen that too. I seemed to have happened with the recent changes to CompositeParser2 that were necessary because of the introduction of Symbol in InvokationMirror. Not sure exactly what the problem is. Looks like CompositeParser2 does not work properly anymore.

That's also the reason why I moved CompositeParser2 to a beta package to discourage people from using it. I hope you are not yet depending on it? Also not sure what your opinion on the magic of CompositeParser2 is? For me it looks cool to be able to refer to productions using variable names, but the warnings of the editor annoy me.

I wil try to investigate the problem the coming weekend. In the meantime, if you see a fix feel free to send me a pull request.

@kevmoo
Copy link
Contributor Author

kevmoo commented May 1, 2013

My haml impl needs to evaluate Dart expressions.

As a work-around, I've been copying from you using the old format

https://github.com/kevmoo/haml.dart/blob/master/lib/dart_grammar.dart

I'd love to have one impl of a Dart parser.

If I get an itch, I'll see if I can help you debug.

@kevmoo
Copy link
Contributor Author

kevmoo commented May 2, 2013

So.

There seems to be a bug in the collection classes...or I'm blind.

I added the following

    _todo.forEach((i) {
      assert(!_done.contains(i));
    });

to _ParserIterator and the assert fails. Some how dupes are getting added to _todo.

I hacked around the issue to fix the assert and notice that this never seems to settle down.

The iteration gets into 1000 "done" items with no hint of finishing.

Possible bug in the grammar?

screen shot 2013-05-01 at 9 28 15 pm

@renggli
Copy link
Member

renggli commented May 2, 2013

I close this issue, as we do not remove duplicates any longer from composite grammars, so the described problem is gone. I created Issue 11 to track the (strangely) slow performance of removeDuplicates(Parser).

@renggli renggli closed this as completed May 2, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants