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.
None of the overloads for
Task.<T>par(...)allow specifying a string description. The underlying implementation,Par2Task, etc. have thedescfield, 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.