Use jaarg alloc-less API, removing BTreeMap middleman.#41
Merged
Conversation
auto-merge was automatically disabled
November 26, 2025 05:02
Head branch was pushed to by a user without write access
ScrelliCopter
force-pushed
the
jaarg-nobtree
branch
from
928c797 to
3a9264d
Compare
azenla
approved these changes
Nov 26, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The current jaarg usage uses the BTreeMap API, this PR moves to the base parsing API which removes the loop and BTreeMap lookup element of argument handling. There's still some string copies to deal with handler scope but that's okay as the map API was internally copying strings anyway, and this means string IDs can be replaced with a simple enum.