Support symbolic record fields when converting to record syntax#4978
Merged
Conversation
fendor
approved these changes
Jun 18, 2026
fendor
left a comment
fendor
left a comment
Collaborator
There was a problem hiding this comment.
LGTM, except for the test failures ;)
olaberglund
force-pushed
the
ola/push-szylsvulzzxv
branch
2 times, most recently
from
f530e58 to
17fe512
Compare
extend test extend test exp
fendor
force-pushed
the
ola/push-szylsvulzzxv
branch
from
17fe512 to
b1ff9fd
Compare
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
2 participants
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 #4975
If the field name consists of symbolic characters, add surrounding parentheses before rendering inlay hint or field with argument when converting to record syntax.
Extended relevant test case to feature a record field made up of symbolic characters.