feat(compiler): Target-neutral emission and Rust code generation#562
Merged
Conversation
Make compilation target-neutral and dispatch bytecode, Rust, and TypeScript emission through explicit target configurations. Add the always-on semantic verifier, migrate all consumers, and consolidate emission sources and fixtures for the 0.4 API.
zharinov
marked this pull request as ready for review
July 10, 2026 17:39
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
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.
This PR makes Plotnik compilation target-neutral.
Previously,
CompiledQuerycontained encoded bytecode and a decodedModule. Every source target therefore paid for a bytecode round trip, andModule::loadacted as the final compiler correctness gate.CompiledQuerynow retains a canonicalSemanticNfa.emit(config)selects bytecode or Rust module generation, whileemit_types(config)selects Rust or TypeScript types. Source targets no longer encode or load bytecode.Removing the bytecode gate required an always-on verifier over the semantic NFA. It validates effect stacks, calls, cursor depth, zero-width behavior, capture layouts, state bounds, and native regex compilation in debug and release builds. Representation-specific limits now belong to their targets; for example, 256 fields can emit Rust and TypeScript while being rejected by bytecode.
Generated Rust executes the same semantic NFA used by the VM and is checked against the VM conformance corpus. The CLI, proc macro, wasm playground, fuzzing, fixtures, and documentation now use the explicit emission API.