Error in XmlNode class declaration about dart-petitparser HOT 13 CLOSED

Changing the base class from 'IterableBase' back to 'Iterable' seems to make the runtime happy. But I'm not sure what this does to the intended functionality.

from dart-petitparser.

Scratch that. The same thing happens when it extends 'Iterable'.

from dart-petitparser.

I've observed the problem in the past too. Seems to be an issue in the IDE only, the runtime was never affected. I cannot currently reproduce it anymore with Dart SDK version 0.5.1.0_r22072.

from dart-petitparser.

I'm still seeing the issue in 22072 on Windows 7:

from dart-petitparser.

I hate to keep harping on this one, but it seems to be occurring again on r22659, if you run all_test_html.dart in checked mode using a Dartium launch. Not sure if this is a problem that only I am having, or whether this is an SDK issue.

from dart-petitparser.

As mentioned before, if you make XmlNode extend Iterable, instead of IterableBase, and remove the mixin reference to the _XmlWritable class, then everything works.

from dart-petitparser.

On Dart SDK version 0.5.7.2_r22611 is definitely does not happen for me. I am updating to r22659 now.

from dart-petitparser.

It doesn't happen for me on Dart SDK version 0.5.7.3_r22659 either. Neither on my OS X development machine, nor on my Linux build server (http://jenkins.lukas-renggli.ch/view/Dart/job/PetitParserDart/).

Did you run "pub update"?

from dart-petitparser.

Yes. I have run pub update; I've cleared my cache and pubspec.lock file and run pub install, too. It's happening for me on both my Windows and my OS X machine. Are you running your tests from the command line, or from a browser? I only see the problem when running tests from the browser.

Also, it doesn't occur on a JavaScript launch, just the VM.

from dart-petitparser.

Indeed, I also get the error in Dartium. Not in JavaScript, not from the command line, and not in the IDE though. Looks like a bug in Dartium then. Care to file a bug?

from dart-petitparser.

Will do. Oddly enough, if I create a clean web project with a class that refers to itself in the generic type parameter, it runs fine. So I'm wondering if the Dart team will need a more complex example in order to repro the issue. It's already been covered in their issue 1222, which was closed in January 2012.

from dart-petitparser.

I opened a bug on the dart site. It is Issue 10717.

from dart-petitparser.

Thank you, I starred the issue.

from dart-petitparser.