Add param name subsection - #9
Open
bvisness wants to merge 2 commits into
Open
Conversation
bvisness
marked this pull request as draft
August 14, 2026 17:24
Collaborator
Author
|
Oh, joyous day, I have just realized that tag types also use |
Collaborator
Author
|
Actually, because tags use function types, this is still fine as is. Apologies for the noise. That said, we might need to discuss what to do with tags a bit more in #4. |
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.
Adds a param name subsection specifically for parameters declared in function types.
Unlike #7, this PR simply adds a new subsection, rather than attempting to extend the behavior of the field name subsection. To me this feels more natural because it avoids confusion about index spaces, aggregate vs. composite types, etc. In particular, it avoids the need to define a new, proper index space that is only used for names, or to extend the definition of an existing address space in a similar way.
Resolves #4.