refactor: move Rust value composition behind language dispatch - #259
Merged
Conversation
Keep recursive depth and cycle handling in DwarfAnalyzer while moving Rust aggregate and enum payload policy into the Rust language module. This keeps non-Rust types on the native DWARF path and makes future language-specific composition explicit.
Move variant applicability out of DwarfAnalyzer and distinguish an unhandled capture from a language-owned capture with no nested plan. This preserves fallback behavior while keeping recursive orchestration generic.
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
DwarfAnalyzerTesting
cargo fmt --allCARGO_TARGET_DIR=/tmp/ghostscope-codex-target cargo test -p ghostscope-dwarf --lib(261 passed)CARGO_TARGET_DIR=/tmp/ghostscope-codex-target cargo clippy --all-targets --all-features -- -D warnings2b68b5b45809