-
Notifications
You must be signed in to change notification settings - Fork 1
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
Annoying type signatures for .sets
, .maps
etc.
#61
Comments
The new API looks like this:
The idea is not to specify the type parameter This has gone out in release 1.13.0, Git commit SHA 1ffdf8c. |
There is a similar problem in getting the Java form of the API from a Scala |
The fix went out in release 1.13.1, Git commit SHA 24ac99e. |
As of 1.12.0,
Trials
has the following methods for building trials of sets and maps:I can't remember now just why the wildcard types were thought necessary, other than that this may have been forced due to the odd lack of covariance in the Scala
Set
andMap
classes - or was it to work with the Java API?Whatever the reason - it is annoying having to workaround the wildcard types, either by propagating them around test code, or doing
.asInstanceOf
to cast to the real type.Worth a spike to see what the problem was and if it can be sorted out...
The text was updated successfully, but these errors were encountered: