Paul Holser
Paul Holser
@Sir4ur0n What do you think of option 3: same as option 2, but deprecate the `List` signature of `shrink`? Idea being that we don't force generator writers to break right...
I would imagine removing the `List` version as 1.0 becomes available.
@Sir4ur0n I don't have any particular time in mind for committing to a 1.0 release.
@spodkowinski Thanks for this -- sorry I'm so late in responding. I am leaning toward option 1 above. Will experiment with it a bit and see how it works.
@spodkowinski The tricky part, I think, will be how to handle generated objects that never make it to a `PropertyVerifier`. For example: - In the presence of a `@When(satisfies =...
@spodkowinski Should a "disposal" swallow any exceptions that it may raise? Log them?
@spodkowinski I'm beginning to wonder whether or not leaving this capability out hinders the functionality of junit-quickcheck enough to warrant adding the additional complexity. What workarounds are there? Property methods...
@spodkowinski @m0smith One option might be to create a `Rule` that can hold values to be deallocated: ```java public static class FileDisposer extends ExternalResource { private final List candidates =...
@spodkowinski The rule would wrap each trial, including shrinks. Thus, its `after` method would follow every trial. The rule won't catch any values filtered by the methods mentioned above.
@mikera Thanks for checking out junit-quickcheck. I don't plan to develop on it any further -- you may want to investigate Jqwik by @jqwik-team. That said, I'd be interested to...