Fix to use Dart 2 core library lowercase constant names.#272
Fix to use Dart 2 core library lowercase constant names.#272munificent wants to merge 1 commit intodart-gde:masterfrom munificent:fix-dart-2-constants
Conversation
|
Hey Bob it looks like this change is failing the build. It looks like it is just a couple unused imports, would you mind fixing that? |
|
Those unused import hints are cascaded errors because it doesn't realize that I could change the config to use the latest dev channel build but that's going to cause massive failures. The code generation tools in this package are nowhere near being strong mode clean or Dart 2 ready. I spent some time trying to make it strong mode clean but it was a rathole and I gave up. The problem is that it's using Parser in a very dynamic way (basically using The generated code that is used at runtime is fine in Dart, though, which is what really matters for users of the package. |
|
Appreciate that you took even that much of a look. In truth, none of the current maintainers (none of us were original authors) have enough context to be able to address most of the Dart 2 related issues because as you point out, this package really takes advantage of the dynamism of Dart 1. Let me circle back with Ben and Oscar and see what we think can be done. Obviously, getting constant fixed should be an easy thing to do, but this PR is bringing a latent issue to the forefront and I wanna make sure we have a plan. |
|
For what it's worth, I got really close to having the whole thing Dart 2 clean. There were only a couple of grammar productions that were weird. So it should be doable and it's mostly a mechanical effort — adding lots of type arguments to places that currently just say |
|
@munificent – just need to switch travis over to use dev instead of stable...or wait until next week 😄 |
|
Dart 2 landed, this should pass checks now? |
No description provided.