You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
None of the overloads for Task.<T>par(...) allow specifying a string description. The underlying implementation, Par2Task, etc. have the desc field, which is simply set to something like par, par2, etc. When looking at a trace, this makes it hard to understand where a parallel task is defined in the code.
Is there a fundamental reason why there are no overloads for Task.<T>par(...) which accept a human-readable description? I'm happy to add these overloads if there's no objection.
The text was updated successfully, but these errors were encountered:
@r00pal that's correct, but you can't name the actual parent task that runs task1 and task2 in parallel. It would still be helpful to see names of the groupings.
None of the overloads for
Task.<T>par(...)
allow specifying a string description. The underlying implementation,Par2Task
, etc. have thedesc
field, which is simply set to something likepar
,par2
, etc. When looking at a trace, this makes it hard to understand where a parallel task is defined in the code.Is there a fundamental reason why there are no overloads for
Task.<T>par(...)
which accept a human-readable description? I'm happy to add these overloads if there's no objection.The text was updated successfully, but these errors were encountered: