Closed devoncarew closed 5 years ago
cc @lambdabaa
@devoncarew There are also tons of errors coming out of dartanalyzer
for me locally after landing the initial revision. Is there initial project configuration needed beyond pub get
? Do we need an analysis options file?
Great, thanks! My only question is about
pub run test
. Does that assume that your entrypoint istest/all.dart
? It does seem to run all of the tests correctly.
package:test uses the analyzer (I believe w/o resolution) to scan files in test/
and determine which are tests. Having an test/all.dart
which delegates to all other tests isn't necessary (but I don't believe can hurt).
@devoncarew There are also tons of errors coming out of
dartanalyzer
for me locally after landing the initial revision. Is there initial project configuration needed beyondpub get
? Do we need an analysis options file?
I see one failure in the CI on this PR:
https://travis-ci.org/dart-lang/tflite_native/builds/560757540#L507
Which I didn't address, as I think your in-progress PR will fix it.
We don't need an analysis options file locally unless we want to tighten things down to be more restrictive. I'd suggest we look into that after this lands, if desired.
there are also tons of errors coming out of dartanalyzer for me locally
It shouldn't need any more config than pub get
. What are the errors?
Also, I don't know how well dart:ffi will analyze...
And, I think you'll need to merge this PR.
It shouldn't need any more config than
pub get
. What are the errors?
Interestingly they aren't showing up on CI, so we can land. I'll also go ahead and add you as a collaborator. Thanks!