fix: duplicate rename colliding with explicit name (Issue #233) - #245
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
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.
Closes #233.
What:
parseHeaderregistra cada nombre emitido (bare + generados) y sube el sufijo_Nhasta único.a,a,a_2→a,a_2,a_2_2en vez de morir conduplicate column name.src/loader.zig: setemitted+ loop de sufijo; cubre loader y modes columns/sample/validate.build.zig: test 19b espejo con header en colisión.Test:
1,2,3exit 0, warnings por rename; caso viejovalue→value_2intacto.zig build unit-testyzig build testexit 0.