Sema: Distinguish implicitly visible memory layouts from the typical @frozen ones
#85868
+263
−160
Conversation
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
xymus
requested review from
hborla,
slavapestov,
tshortli and
xedin
as code owners
Contributor
Author
|
@swift-ci Please smoke test |
xymus
force-pushed
the
exportability-nle-split
branch
from
7f25ca3 to
e3571eb
Compare
Contributor
Author
|
@swift-ci Please smoke test |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Refactor logic tracking memory layouts visible to clients to differentiate when they are explicitly set visible with
publicor@frozen, and when they are implicitly public (in non-library-evolution mode for a type without@_implementationOnly). This extra information is then used to customize the implicit use case behavior: providing a more precise diagnostics and allowing reference SPI and non-publicly imported decls.