[pull] swiftwasm from master #1791
Merged
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
![pull[bot]](https://avatars.githubusercontent.com/in/12910?s=60&v=4){kind=small}
…acking property wrapper before all of self is initialized if the wrapper has already been initialized.
Reject concurrency-only attributes in the parser if the experimental concurrency mode is not enabled.
Introduce a new attribute `@actorIndependent` that specifies that a given declaration is considered to be independent of any actor. Actor-independent declarations do not have access to actor-isolated state, even when they are declared as instance members of the actor. On the other hand, actor-independent declarations can be used to conform to (synchronous) requirements in protocols.
…b assert-build And rename COWSanityChecks -> COWChecks. rdar://problem/68181747
…to help debug failures on bots. Just a quick hack to ease debugging on the bots.
…independent [Concurrency] Introduce `@actorIndependent` attribute.
Now that the top-level source file is the only dependency source that matters, the only case that matters is when request evaluation enters a primary file. For non-primaries, there will be no corresponding swiftdeps file to emit references into, so we're just wasting time and memory keeping track of anything that happens there. This is only possible after we removed cascading dependencies because unqualified lookups had to be charged to the files they originated in. Now, we charge those lookups to the primary that initiated the request.
…72f8107016cda0a4e839737
Drop Legacy Cascading Dependencies From the Frontend
The final set of edges that were being registered cascading were external edges. Just mark these all private - they're duplicated into the swiftdeps for each file that imports a given (usually clang) module anyways.
Now that the frontend no longer produces these edges, we do not need to assert about them.
This is no longer a meaningful distinction.
Only external edges need this.
…ialized witness Deserialized computed properties don't get a PatternBindingDecl apparently. Fixes <rdar://problem/68241758>.
…res with implicit returns too (swiftlang#33604) * [SILGen] Emit unreachable code diagnostics for single expression closures with implicit returns too * [Test] Update diagnostic in test/SILGen/functions_uninhabited_param.swift
…hout -enable-library-evolution (swiftlang#33443)
…ring [Property Wrappers] Refine assign_by_wrapper lowering
…ing-crash-no-pbd Sema: Fix crash on static -vs- non-static witness mismatch with deserialized witness
…alls Excise Remaining Usages of Legacy Cascading Dependencies From Frontend
kateinoigakukun
approved these changes
Sep 22, 2020
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.
See Commits and Changes for more details.
Created by
pull[bot]. Want to support this open source service? Please star it : )