Re: Avoiding Side Effects of ForkJoinPool.managedBlock

2024-01-18 Thread David Holmes
On 18/01/2024 7:30 pm, Johannes Spangenberg wrote: Hello, I have a question about dealing with side effects caused by ForkJoinPool. I am not certain if this mailing list is the appropriate platform, but I hope it is. The issue I am facing is that running code within a ForkJoinPool may change t

Re: Avoiding Side Effects of ForkJoinPool.managedBlock

2024-01-18 Thread Johannes Spangenberg
> On the REE, this is also controlled by JUnit when it creates the FJP. > The saturate parameter is the predicate that is determines if REE is > thrown or the pool continues without an additional thread. Thanks, I missed that unfortunately. My version of JUnit uses null for the saturate parameter,

Re: Avoiding Side Effects of ForkJoinPool.managedBlock

2024-01-18 Thread Alan Bateman
On 18/01/2024 09:30, Johannes Spangenberg wrote: Hello, I have a question about dealing with side effects caused by ForkJoinPool. I am not certain if this mailing list is the appropriate platform, but I hope it is. The issue I am facing is that running code within a ForkJoinPool may change the

Avoiding Side Effects of ForkJoinPool.managedBlock

2024-01-18 Thread Johannes Spangenberg
Hello, I have a question about dealing with side effects caused by ForkJoinPool. I am not certain if this mailing list is the appropriate platform, but I hope it is. The issue I am facing is that running code within a ForkJoinPool may change the behavior of the code. These changes in behavior h