Only import propBoolean from Prop

[travisbrown]

I noticed this because of a change in Dotty that I think is a bug, but I think it's the right thing to do anyway, since importing Prop._ brings in a lot of other definitions that aren't needed.

[travisbrown]

I pushed a commit changing the JDK for Travis CI to avoid Oracle's (which hasn't been available on Travis CI for a while).

[fthomas]

I agree that only importing definitions that are needed is generally better. Prop._ also includes the AnyOperators implicit conversion which I believe allows to write properties like this (notice the ?=):

prop> (i: Int) => Test.f(i) ?= (i * 2)

instead of:

prop> (i: Int) => Test.f(i) == (i * 2)

Maybe AnyOperators should be imported too, to minimize breaking existing doctests.
WDYT @travisbrown?

[travisbrown]

@fthomas The problem is that if we don't use the wildcard import then we'll get an unused import warning / failure for AnyOperators. I've never used prop> with sbt-doctest, just the scala> ... res0: ... style. I guess we could use import org.scalacheck.Prop.{BooleanOperators => _, _}?

[fthomas]

import org.scalacheck.Prop.{BooleanOperators => _, _} seems fine to me.

[travisbrown]

@fthomas Sounds good, done!

[travisbrown]

@tkawachi Hi! Any chance we could get a release with this change and #132? I'm happy to help in any way I can.

[tkawachi]

@travisbrown Thank you for the PR. Please try 0.9.6 which I just published.

[travisbrown]

@tkawachi I just tried it out in a project where I was seeing warnings, and they're gone. Thanks much!