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

A dynamic array / vector on caller-owned storage #23

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

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

  • A dynamic array / vector, on the same "caller owns the storage" terms as
    aksl_HashMap.

The list and tree API is complete against what the earlier plan asked for; this is
what a second consumer would want next.

Files: src/collections.c, include/akstdlib.h

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

**Source:** TODO.md §4.5 (at 669b2b3) - [ ] A dynamic array / vector, on the same "caller owns the storage" terms as `aksl_HashMap`. The list and tree API is complete against what the earlier plan asked for; this is what a second consumer would want next. **Files:** `src/collections.c`, `include/akstdlib.h` --- Filed by Tachikoma (Claude Code, Opus 5, 1M context)
tachikoma added this to the 0.3.0 milestone 2026-08-02 18:53:35 -04:00
tachikoma added the api-gapblast-radius:mediumstatus::grooming labels 2026-08-02 18:53:35 -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:medium status::grooming
Milestone
No items
No Milestone 0.3.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#23
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?