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

Enable generics in waitFor #130

Closed
travissanderson-wf opened this issue Jan 10, 2017 · 8 comments
Closed

Enable generics in waitFor #130

travissanderson-wf opened this issue Jan 10, 2017 · 8 comments

Comments

@travissanderson-wf
Copy link
Contributor

For consuming libraries to obey strong mode, we will need to enable the commented-out generics in the waitFor definition here. This would require bumping the SDK restriction to 1.21+. Is this a change you would be open to accepting?

@DrMarcII
Copy link
Contributor

Yes.

@travissanderson-wf
Copy link
Contributor Author

the code change is pretty trivial, just uncommenting the generic definitions already in there for the most part, but I have no idea how to get bazel running tests in a Dart 1.21 environment

@DrMarcII
Copy link
Contributor

dart_rules are currently using 1.21.0-dev.3.0 (https://github.com/dart-lang/rules_dart/blob/master/dart/build_rules/repositories.bzl#L69). Is that not sufficient?

@travissanderson-wf
Copy link
Contributor Author

That should be, when I run bazel test locally this is the type of error I am seeing though:

FAIL: //test:io_test_chromium-native (see /private/var/tmp/_bazel_travissanderson/48afd87cd8d3f5caedafcff5ca1c95db/execroot/webdriver.dart/bazel-out/local-fastbuild/testlogs/test/io_test_chromium-native/test.log).
'package:webdriver/support/async.dart': error: line 28 pos 18: generic functions not supported
Future<T> waitFor<T>(T condition(),

@travissanderson-wf
Copy link
Contributor Author

I opened a PR to see if travis-ci does better than local-guy-named-travis #131

@travissanderson-wf
Copy link
Contributor Author

travissanderson-wf commented Jan 11, 2017

This was addressed by 131, would you be able to publish a release including this change at your convenience? thanks! @DrMarcII

@DrMarcII
Copy link
Contributor

Release has been published.

@travissanderson-wf
Copy link
Contributor Author

Thanks!

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