-
Notifications
You must be signed in to change notification settings - Fork 616
ModuleDef and schema changes to support procedures #3392
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
gefjon
wants to merge
10
commits into
master
Choose a base branch
from
phoebe/procedure/moduledef
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
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
This commit extends various schema and schema-adjacent structures to describe procedures, a new kind of database function which are allowed to perform side effects. This includes extending `RawModuleDefV9` with a way to register `RawProcedureDefV9`s in the `misc_exports`, preserving compatibility with modules that predate procedures. The module validation path is reorganized somewhat to validate various properties related to procedures while preserving code clarity and maintainability. Additionally, the `ArgsTuple` machinery for ser/de-ing reducer arguments using the argument type as a seed is extended to also support procedure arguments. All of this is currently unused.
Centril
reviewed
Oct 15, 2025
Prior to this commit, we never actually checked that reducers had unique names. My new `check_function_names_are_unique` assumed this invariant, but we were silently ignoring duplicate reducer names. With this commit, `check_function_names_are_unique` actually validates uniqueness not only between the two sets, but within them. This commit also adds three tests for the three possible ways to have a duplicate name: two reducers, two procedures, or one of each.
joshua-spacetime
approved these changes
Oct 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description of Changes
This commit extends various schema and schema-adjacent structures to describe procedures, a new kind of database function which are allowed to perform side effects.
This includes extending
RawModuleDefV9
with a way to registerRawProcedureDefV9
s in themisc_exports
, preserving compatibility with modules that predate procedures.The module validation path is reorganized somewhat to validate various properties related to procedures while preserving code clarity and maintainability.
Additionally, the
ArgsTuple
machinery for ser/de-ing reducer arguments using the argument type as a seed is extended to also support procedure arguments.All of this is currently unused.
API and ABI breaking changes
Additive and backwards-compatible additions to
RawModuleDefV9
and friends.Expected complexity level and risk
2 - some minor complexity in schema validation which may have gotten borked in a merge at some point.
Testing
Unsure what tests would be useful, open to suggestions from reviewers.