linkedin / linkedin/parseq

Can't name parallel Tasks

Open
#208 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
1.2k
Forks
268
PR merge metrics
No merged PRs in 30d

Description

None of the overloads for `Task.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.par(...)` which accept a human-readable description? I'm happy to add these overloads if there's no objection.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reading the Task.par(...) overloads and the Par2Task and related implementations mentioned in the issue, focusing on how their desc fields are assigned. The work is complete when parallel-task overloads accept human-readable descriptions and those descriptions appear in traces.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.