andrew/libakstdlib
1
0
Fork 0
Code Issues 26 Pull Requests Actions Packages Projects Releases Wiki Activity

Wrap threads -- blocked on the error pool #19

New Issue
Open
opened 2026-08-02 18:53:31 -04:00 by tachikoma · 0 comments
tachikoma commented 2026-08-02 18:53:31 -04:00
Collaborator
Copy Link

Source: TODO.md §4.4 (at 669b2b3)

  • pthread_create/join/detach
  • pthread_mutex_*, pthread_cond_*, pthread_rwlock_*
  • sem_*

Blocked on the unlocked error pool. A threading API nobody can call from a
thread is not an API, so this cannot start until that is resolved -- see the pool
issue in this tracker and its upstream counterpart in libakerror.

Files: src/, include/akstdlib.h

Filed by Tachikoma (Claude Code, Opus 5, 1M context)

**Source:** TODO.md §4.4 (at 669b2b3) - [ ] `pthread_create`/`join`/`detach` - [ ] `pthread_mutex_*`, `pthread_cond_*`, `pthread_rwlock_*` - [ ] `sem_*` **Blocked on the unlocked error pool.** A threading API nobody can call from a thread is not an API, so this cannot start until that is resolved -- see the pool issue in this tracker and its upstream counterpart in libakerror. **Files:** `src/`, `include/akstdlib.h` --- Filed by Tachikoma (Claude Code, Opus 5, 1M context)
tachikoma added this to the 1.0.0 milestone 2026-08-02 18:53:31 -04:00
tachikoma added the api-gapblast-radius:highstatus::grooming labels 2026-08-02 18:53:31 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
abi-break
Cannot land without a soname bump
 api-gap
A caller cannot express something
 blast-radius:high
Ordering: highest blast radius
 blast-radius:low
Ordering: lowest blast radius
 blast-radius:medium
Ordering: middling blast radius
 defect
Wrong behaviour reachable from the public API
 design-decision
Needs a decision written down before code
 docs
Documentation, comments, AGENTS.md
 hygiene
Style, dead code, consistency
 packaging
Build, install, pkg-config, CMake config
 performance
Has a measurement behind it
 status::blocked
Waiting on something else -- a decision, a dependency, or another issue
 status::grooming
Not yet worked out: scope, approach or priority still being settled
 status::ready
Understood well enough to start: scope and approach are settled
 test-coverage
A gap in the suites, not a defect
No Label api-gap blast-radius:high status::grooming
Milestone
No items
No Milestone 1.0.0
Projects
Clear projects
No project
Assignees
Clear assignees
tachikoma andrew
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: andrew/libakstdlib#19
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?