Closed computablee closed 11 months ago
I would like to work on this issue. Will you please assign it to me?
Absolutely! When opening your PR, just please make sure to target the bug-fixes
branch.
Sure! Thank You!
@Myworld21 I'm just checking in, do you have any updates?
I would like to take on this task if @Myworld21 is no longer working on it
@Kaybangz Sure, I'll assign you as well. You can just add it to your current PR if you like, it'll be a really good error handling PR.
Update: when working on exception handling tonight I inadvertently fixed this issue. I am unassigning everyone and closing this issue.
@Kaybangz Since I accidentally fixed this issue right after assigning you, let me know if there's another issue you want to work on and I'll see what I can make happen. So sorry!
In the last major refactor of the DotMP core, I neglected to re-add the exception handling for
DotMP.Parallel.For
andDotMP.Parallel.ForReduction
if they are nested within each other. You should check theWorkShare
singleton'sin_for
flag and throw theCannotPerformNestedForException
if it's set. Shouldn't be difficult, but you want to make sure to instantiate aWorkShare
object using the default constructor to check thein_for
flag before the parameterized constructor is called, because calling the parameterized constructor resets the staticWorkShare
fields.You can skim the
WorkShare
class in theInit.cs
file to see what I mean.