-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[IRGen] Improvements to function type metadata #12500
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
b33a6c7
[IRGen] Add parameter flags to function type metadata
xedin 99f188e
[IRGen] Switch function metdata to use `Metdata *` for parameter refe…
xedin 728d2a4
[IRGen] Fix function metadata endpoints to use separate parameter/fla…
xedin f6b0d2d
[ABI/IRGen] Add custom function parameter flags representation for me…
xedin 801b35e
[ABI/Runtime] NFC: Rename function metadata arguments to parameters
xedin e80455e
[RemoteAST] Fix metadata reader to properly read function metadata
xedin 0685106
[Casting] NFC: add some more tests for functions with parameter flags
xedin fbd502a
[AST] NFC: Remote unused accessor methods from `ParameterTypeFlags`
xedin File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you'll need to change the createFunctionType API to also take parameter flags, which probably means remapping them to the AST flags.
Also, what I mean about TupleMetadata is that you should modify the
MetadataKind::Function
case inreadMetadata
to start by reading the FunctionTypeMetadata and then use that to figure out the complete size to read, like the case forMetadataKind::Tuple
does.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah ok, I think I understand know, I thought you meant treat flags like labels are treated in case of tuple...
Regarding
createFunctionType
API - each of the elements inParameters
already has flags attached to it, so I think flags are covered that way?...There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, yes, I see, that makes sense.