Add Native Auto Splitter Runtime Support#135
Draft
CryZe wants to merge 1 commit into
Draft
Conversation
This allows auto splitters to run outside the WebAssembly sandbox as native programs while keeping the existing WebAssembly import API intact. Native builds use platform process access directly and delegate timer integration, logging, settings, and tick scheduling through a host-provided runtime trait. The CI now builds native targets explicitly so native regressions are caught alongside the existing WebAssembly coverage. The workflows use rustup directly instead of the deprecated Rust setup action.
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
1 participant
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.
Summary
This adds native execution support for auto splitters without changing the existing WebAssembly import API. Native builds can use platform process access directly from
asr, while timer integration, logging, settings, and tick scheduling are delegated to a host-provided runtime trait.The GitHub Actions build workflow now also builds the crate natively on stable and nightly with no default features, default features, and all features. This keeps native regressions covered alongside the existing WebAssembly targets.
The workflows now use
rustupdirectly instead of the deprecated Rust setup action.Validation
cargo check --all-featurescargo test --all-features --libcargo clippy --libcargo check --target wasm32-unknown-unknowncargo check --target wasm32-unknown-unknown --features alloccargo check --target wasm32-unknown-unknown --all-featurescargo check --target wasm32-wasip1cargo check --target wasm32-wasip1 --features alloc,wasi-no-stdcargo check --target wasm32-wasip1 --all-featurescargo build --no-default-featurescargo buildcargo build --all-featuresNotes: the local runs still emit the existing
wasisemver metadata warning, existingwasi_no_std.rswarnings on WASI all-features, and Windows incremental compilation cleanup warnings.