Repository navigation
Complete bytes analysis with compiler-based function identities - #10
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.
utgen analyzeexported 663 bytes functions but only 226 context files, then failed validation. Trait-default contexts were never written; short-name matching conflated generic/reference impls; forwarding-macro methods were absent from the source AST.Local validation passed: release and debug workspace builds; 30 workspace tests (one live-model test ignored); the minimal generation/repair/coverage pipeline; and the method-identity fixture. Both bytes copies passed with all 663 branch records, dependency records, compiler identities, and contexts aligned, in 34.632 s and 34.747 s. The previous release baseline failed after 43.714 s with only 226 contexts; these figures are not a speedup benchmark because successful work differs.
Both the branch CI and PR CI passed, including the existing coverage/scheduling regressions and the new release analysis check. On the PR runner, the bytes copies completed in 25.401 s and 24.551 s, with all artifact, identity, and source-preservation assertions passing. No model service is required for the bytes check. The scope is the pinned bytes default configuration; recovering parseable method source does not implement general macro expansion or validate bytes model-generation quality.