From a6cdfa18de85f33bbed15717e65019d43e47c334 Mon Sep 17 00:00:00 2001 From: Johannes Link Date: Wed, 24 Apr 2024 14:56:49 +0200 Subject: [PATCH] Corrected some outdated part in the user guide --- documentation/src/docs/include/using-arbitraries-directly.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/src/docs/include/using-arbitraries-directly.md b/documentation/src/docs/include/using-arbitraries-directly.md index 7e6ecb727..4bf6e930e 100644 --- a/documentation/src/docs/include/using-arbitraries-directly.md +++ b/documentation/src/docs/include/using-arbitraries-directly.md @@ -91,7 +91,7 @@ Currently this API consists of a few static methods on class `net.jqwik.api.sess - `JqwikSession.isActive()`: Check is a session is currently active. - `JqwikSession.finish()`: Finish the currently active session, thereby releasing all the implicitly used memory space. - `JqwikSession.finishTry()`: Announce that you're done with the current `trie` of a property. - This will, for example, reset the uniqueness collector of a generator for collections. + This will, among other things, reset all [stores](#lifecycle-storage) that use `Lifespan.TRY`. - `JqwikSession.run(Runnable code)`: Wrap the runnable code segment in implicit `start()` and `finish()` calls. Mind that there's currently no way to use nested sessions, spread the same session across threads