feat: add extension function mechanism (Phase 1) #26
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/extension-interface"
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?
Introduce a principled mechanism for registering external pure functions
callable from
bindexpressions during grounding. This is the foundationfor aggregation and other extension use-cases.
supporting types in new function_registry module
EvalContext through the grounding call chain
behave identically (1827 existing tests pass unchanged)
Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com
fix: remove redundant Arity::describe(), fix pluralization, add test coverage
call in body predicate argument, and zero-arg function
Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com
test: add extension function test coverage for non-integer returns, e2e reasoning, multi-function
Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com
fix: struct initialisation
View command line instructions
Manual merge helper
Use this merge commit message when completing the merge manually.
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.