forked from apple/swift
-
Notifications
You must be signed in to change notification settings - Fork 28
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
Merge main 2023-01-11 #5170
Merged
Merged
Merge main 2023-01-11 #5170
Conversation
This file contains 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
In complex situations, a type would not be assigned to an abstract closure that was the declaration context of the declaration being checked. This used to cause crashes because you couldn't query a closure on whether it was an async context if it didn't have a type assigned. This behaviour has been updated to lazily compute the function decl ext info if the type hasn't already been assigned. This means that calling `AbstractClosureExpr::isAsyncContext` is now safe, even when a type has not yet been assigned. The request change was added in commit c3b6160.
…e information If an attribute is inferred from a protocol conformance it won't have any source information, in such cases let's determine where an attribute could have been inserted if it was spelled explicitly and use that location in a synthesized initializer call. Resolves: rdar://103938899
Fixes an assert that was meant for a narrow case and accidentally applied too broadly. This variation of the liveness utilities wasn't being exercised widely, and is difficult to test with valid OSSA.
…th the correct condition.
Fix an assert in MultiDefPrunedLiveness
Make sure liveness reports a complete boundary even for OSSA lifetimes that are incomplete. Definition blocks can be on the liveness boundary in this case.
* Bump Swift Argument Parser checkout to 1.1.2 * Revert release/5.7 back to using swift-argument-parser 1.0.3 * Bump to 1.1.4 * Bump version
Fix MultiDefPrunedLiveness; add boundaries for dead end blocks.
[Sema] RuntimeMetadata: Make sure that inferred attributes have sourc…
…tandard library. Older versions of the 5.8 compiler have a bug when generating SIL for functions with `@_backDeploy` containing defer blocks (apple#62444) and for now we need the standard library interface to be compatible with those older compilers. Resolves rdar://104045168
…645c8c5d5c72d5df2a1 [move-only-addr] Fix an assert and add some more tests.
…yed-funcs [TaskLocals] Avoid use of `defer` in back deployed functions in the standard library
…-are-alright-now Diagnose unavailable closures without types
Don't make older compilers parse @expression at all
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.
No description provided.