docs/BUILTINS.md: task_spawn row says task_yield/task_join 'land in a later increment'; both exist
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 88/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- c
- Domain
- documentation
Research direction
Start in docs/BUILTINS.md around line 931, in the Concurrency table, and compare the task_spawn, task_yield, and task_join rows. Run a small program with eigenscript to verify when a spawned task runs, then update the outdated parenthetical. Finish by running grep -n "later increment" docs/BUILTINS.md and confirming no Concurrency row still describes task_* as unimplemented.
Written by the indexing model from the issue text.
Description
The task_spawn row in docs/BUILTINS.md (Concurrency table, about line 931) ends with:
(Increment 1a: the task is recorded and reported by
task_alive; the copying-stack scheduler that runs and interleaves tasks —task_yield/task_join— lands in a later increment.)
That increment has shipped. task_yield has its own row three lines further down, and task_join is in the same table. A reader of the task_spawn row is told that tasks do not run yet.
Found while fixing #1362's spawn row, in the same table.
Done when
- The parenthetical is removed, or replaced with one sentence on what a spawned task does now (it runs when the spawner yields, joins or finishes), checked against a small program run with
eigenscript. - No other row in the Concurrency table still describes
task_*as unimplemented. Check withgrep -n "later increment" docs/BUILTINS.md.
- Dominant language
- C
- Stars
- 3
- Forks
- 7
- Avg merge
- 4h 5m
- Merged PRs (30d)
- 116
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from InauguralSystems/EigenScript
-
area:docs good first issue kind:docs-drift
Difficulty 1/5 Under an hour Newbie friendliness 92/100
InauguralSystems/EigenScript#1400 ·
Maintainers usually reply within 1 day
-
area:docs good first issue kind:docs-drift
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
InauguralSystems/EigenScript#1396 ·
Maintainers usually reply within 1 day
-
area:embed kind:silent-wrong
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
InauguralSystems/EigenScript#1387 ·
Maintainers usually reply within 1 day
-
area:stdlib kind:silent-wrong
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
InauguralSystems/EigenScript#1378 ·
Maintainers usually reply within 1 day
-
area:gates kind:gate-defect
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
InauguralSystems/EigenScript#1374 ·
Maintainers usually reply within 1 day
All issues in InauguralSystems/EigenScript
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
python-pillow/Pillow#10087 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
OpenPrinting/cups#1729 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
awslabs/amazon-kinesis-video-streams-webrtc-sdk-c#2406 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
DaveGamble/cJSON#1094 ·
-
status:needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
PX4/PX4-Autopilot#28923 ·
Maintainers usually reply within 1 day