Skip to content

Add managed scalar callback foundation#4

Closed
awakecoding wants to merge 1 commit into
mainfrom
split/core-managed-scalar-callbacks
Closed

Add managed scalar callback foundation#4
awakecoding wants to merge 1 commit into
mainfrom
split/core-managed-scalar-callbacks

Conversation

@awakecoding
Copy link
Copy Markdown
Owner

Summary- Port the managed scalar callback foundation from the all-in-one advanced APIs work.- Add scalar callback ABI/value types, registration/unregistration, scalar runtime invocation, result conversion, deterministic metadata, and prepared-statement invalidation.- Add focused scalar callback integration coverage for fixed and variadic callbacks, argument conversion, null/text/blob/error result conversion, callback error propagation, deterministic metadata, unregister/re-register invalidation, and context/value destructor counts.## ScopeThis PR is limited to managed scalar callback support. It intentionally does not include aggregate support, custom collations, extension-loading changes, SDK-kit changes, .NET exposure/facade/raw changes, workflow changes, or simulator changes.## Validation- cargo fmt --check- git diff --check- cargo check -q -p core_tester --features pure-rust-crypto --test integration_tests- cargo clippy -q -p core_tester --features pure-rust-crypto --test integration_tests -- --deny=warnings- cargo test -q -p core_tester --features pure-rust-crypto --test integration_tests managed_scalar -- --nocaptureAn initial targeted test attempt failed during compilation with rustc-LLVM ERROR: IO failure on output stream: no space on device. That was environmental: build output was moved off the nearly-full C: drive, and all validation above passed afterward.

Port the scalar-only callback foundation for managed external functions, including registration, invocation, result conversion, metadata, invalidation, and focused integration coverage.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@awakecoding
Copy link
Copy Markdown
Owner Author

Closing because this scalar split belongs upstream at tursodatabase/turso.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant