-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[AST] More JSON AST dump improvements. #80498
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
5 commits
Select commit
Hold shift + click to select a range
718f9f0
Improve type USR generation and inheritance dumps.
allevato 9f4fc8c
Print more information about conformances.
allevato fa1f829
Also show the new conformance details in the default dump.
allevato ef6352c
Add a source-file-level mapping of opaque type USRs to equivalent
allevato 5be2498
Address review feedback.
allevato 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
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.
calling getDeclaredInterfaceType() on OpaqueTypeDecl should produce an assertion failure; are you sure you have test coverage for this?
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.
Hmm, it seems to be working? When I dump an
OpaqueTypeDecl
in the context of the declaring function,declared_interface_type
is one of the fields we dump (line ~2158). For this snippet:I get
and the top-level mapping is
There are tests exercising opaque types in the omnibus
Frontend/ast-dump-json-no-crash.swift
test.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 used
getDeclaredInterfaceType()
because it seemed to be the most likely match for what would appear in expressions that use the type, but I'm also happy to switch it to something else more appropriate.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 see, I missed that we set it in OpaqueResultTypeRequest::evaluate(). My apologies.
However, my original concern is that opaque return type can appear in a nested position, and we might have more than one opaque return type, eg:
Indeed, it appears that the declared interface type of the opaque result declaration is the entire return type of the function in this case,
(some Any, some Any)?
, so yourcastTo<OpaqueTypeArchetypeType>()
will fail. You probably want to walk the declared interface type to collect all opaque archetypes that it contains.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, right. Updated this to use
transformRec
to replace anyOpaqueTypeArchetypeType
s with theirgetExistentialType()
, and added a handful of tests that cover different structural situations.