Repository navigation
Conversation
[AUTOMATED] Qualify materialized result keys by address when a name refers to multiple entries. Verify both entries survive the existing C artifact round trip.
This branch has not been deployed
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.
[AUTOMATED]
Reloading a saved artifact kept only the last function when two entries shared a name. Use
name@0xADDRESSkeys for collisions and keep each record's original name, address, and body. Unique names keep their existing keys. This is the artifact-reload slice of #91.The regression writes two same-named functions with the existing writer. It fails on main and passes on
41b5317. The focused suite passed 55 tests. With caching disabled, the full local suite had one additional pass and the same 29 failures and 24 errors as main.