Enthuware

There are two answers that are almost the same, namely:

[*]Subclass RecursiveAction and implement the compute() method that computes the new value but does not return anything.
[*]Implement compute() method in RecursiveAction that computes the new value but does not return anything.


The second answer is marked as correct, but I think the first answer is even more accurate, and therefore correct as well. The question asks what would be a good approach and subclassing RecursiveAction is certainly a good approach (together with answer #6)!

Kind regards,

Martijn

You are right. Fixed.
thank you for your feedback!

Why is option 3

Create a RecursiveAction that subdivides the task and submit all such tasks to a ForkJoinPool.

not correct?
By forking the subtask we're submitting it to the pool. Does the answer intend a new ForkJoinPool (that would make the answer wrong) or am I missing something?

As the explanation says, there is no need to "submit" the tasks to the pool while the option says, "and submit all such tasks to a ForkJoinPool".

HTH,
Paul.

I've read the explanation, my confusion comes from the fact that the solution actually submits the task to the pool via fork() method.

OK, I see now what you mean. You are right. The option is not clear. I have updated it to say "...and submit all such tasks to the pool using submit method".

thank you for your feedback!
Paul.