Gen.chooseNum(0, Int.MaxValue) sometimes gives -1073741823

[shawjef3]

I would expect this to not give any negative values.

[shawjef3]

As a work around, I'm using Gen.choose(0, Int.MaxValue).

[shawjef3]

Actually, Gen.choose isn't a good workaround, because it doesn't test extrema.

[shawjef3]

I'm using scalacheck 1.13.5 for scala 2.11.

[Philippus]

could you share an example? So far, I cannot reproduce this. Maybe it happened during shrinking?

[ashawley]

Agree. I cant 'get the most naive test of this to fail:

    Prop.forAll(Gen.choose(0, Int.MaxValue)) { x: Int =>
      0 <= x && x <= Int.MaxValue
    }

When I intentionally modified the test so it fails, I did see that the shrinking could produce a negative.

> ARG_0: -1
> ARG_0_ORIGINAL: 1967653363

That's a known issue with shrinkers, see #129, not with the generators.

[pford19]

Curious about issue tracking and lifecycle process. Why is this issue still in Open status?

[rickynils]

@pford19 Lack of time. I want to bring in more maintainers and get better project management for ScalaCheck, but I have unfortunately not time for that either.

[pford19]

:-)

[SethTisue]

sounds like maybe we should just close this, since there's no clear issue here that isn't #129?

[non]

Agreed, I think that issue tracks the problem, and -disableLegacyShrinking is a work around for it.

[plokhotnyuk]

@non am I understand correctly that disabling of legacy shrinking is not turned on by default in latest versions?