Repository navigation
Complete SliM execution semantics - #6
Merged
Merged
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
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.
The server previously had branches for all five SliM instructions, but construction, symbol handling, and method dispatch still stopped at string-only named fixtures. This change completes the execution-context semantics needed by SliM V0.5: typed constructors, fixture chaining, recursive symbols, SUT delegation, ordered library fallback, and actor helpers.
Instances, libraries, actors, and symbols now preserve shared
SlimObjectidentity. A whole object-valued class symbol is copied bymakewithout invoking a constructor, including opaque objects; callable fixture objects continue to dispatch through their shared handle. Textual symbol replacement recognizes letter-only names, preserves undefined symbols, handles punctuation and adjacency, walks recursive lists, and is deliberately not applied byassign.Calls resolve against the named fixture, its annotated SUT, user libraries from newest to oldest, and the built-in helper behavior.
getFixture,pushFixture,popFixture, andcloneSymbolsupportscriptTableActorand object symbol workflows. Imports prefer exact class paths and then the newest matching import.The fixture macro now supports multiple
#[slim(constructor)]functions selected by arity, fallible constructors, a zero-argumentDefaultcompatibility path, and#[slim(sut)]. Invalid markers, constructor signatures, SUT signatures, duplicate constructor arities, and unsupported receivers produce checked compile-time diagnostics. Constructor and lookup failures use the documented SliM exception names, and malformed symbol assignments retain their instruction data without executing fixture code.Validation:
cargo test --workspace --all-featurescargo clippy --workspace --all-targets --all-features -- -D warningsgit diff --checkA separate Terra implementation agent and an independent Terra reviewer checked this slice against the local feature-completeness plan, the official SliM V0.5 specification, and FitNesse's reference execution behavior. The final review found no remaining actionable issues.