[pull] swiftwasm-release/5.8 from release/5.8 #5311
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}
We should be able to use static linking here without negatively impacting code size.
…l contextual information becomes available We determine that based on four criteria: - Builder type doesn't have any unresolved generic parameters; - Contextual type associated with the closure doesn't have any unresolved type variables (which means that all possible contextual information is provided to the body); - All of the references to declarations from outer scope are resolved (i.e. a variable declaration from a parent closure); - The contextual result type is either fully resolved or opaque type. If all the criteria a met the conjunction that represents a closure is going to be picked and solved as the next solver step. Resolves: rdar://104645543 (cherry picked from commit f27369d) (cherry picked from commit a815de7) (cherry picked from commit 38f8be1) (cherry picked from commit 5bb9d75) (cherry picked from commit fda7530) (cherry picked from commit b84d70b)
cleanup: no need to dump input always
…er-conjunctions-5.8 [5.8][CSBindings] Solver result builder transformed closures as soon as al…
Emulate the behavior of Swift 5.5/5.6 by default, using `-strict-concurrency=minimal`.
…minimal-cherry [5.8🍒] Use -strict-concurrency=minimal as the default for Swift 5.x mode.
…sil-issue [5.8][Distributed] correct take semantics for synthesized ID assignments
Since all of the branches of an `if` statement are joined together and hence produce the same type, that type should be used to check whether `buildWithAvailability` is required but missing regardless of availability condition kind. Resolves: swiftlang#63764 (cherry picked from commit c4ea02c)
This fixes `ninja check-swift-validation` in the Release+Distribution build as the block name is set under `#ifndef NDEBUG`.
Apparently this issue also affects ARM64_32. rdar://105768086
windows: convert swift-crypto to static linking
[5.8] Fix Test in Release Build
Don't use tsd_private.h in compatibility libraries for ARM64_32.
[5.8][BuilderTransform] Rework missing `buildWithLimitedAvailability` detection
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]
Can you help keep this open source service alive? 💖 Please sponsor : )