Skip to content

Conversation

@tlively
Copy link
Member

@tlively tlively commented Apr 15, 2024

For types that do not have explicit names, we generate index-based names in the
printer. However, we did not previously ensure that the generated types were not
already used as explicit names, so it was possible to print the same name for
multiple types, which is not valid.

Fix the problem by skipping indices that are already used as type names.

Fixes #6492.

For types that do not have explicit names, we generate index-based names in the
printer. However, we did not previously ensure that the generated types were not
already used as explicit names, so it was possible to print the same name for
multiple types, which is not valid.

Fix the problem by skipping indices that are already used as type names.

Fixes #6492.
@tlively tlively requested a review from kripken April 15, 2024 06:28
Copy link
Member Author

tlively commented Apr 15, 2024

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @tlively and the rest of your teammates on Graphite Graphite

@tlively tlively merged commit e460877 into main Apr 16, 2024
@tlively tlively deleted the fresh-type-names branch April 16, 2024 08:08
@gkdn gkdn mentioned this pull request Aug 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

WATParser bug when parse implicit type definition

3 participants