Skip to content

[pull] swiftwasm from master #1090

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 3 commits into from
May 25, 2020
Merged

[pull] swiftwasm from master #1090

merged 3 commits into from
May 25, 2020

Conversation

pull[bot]
Copy link

@pull pull bot commented May 24, 2020

See Commits and Changes for more details.


Created by pull[bot]. Want to support this open source service? Please star it : )

compnerd added 2 commits May 23, 2020 16:45
The variable was supported to be set to the triple, except it was set to
the variable itself, effectively setting the variable to nothing.  This
is needed to clear the path to directory style installation for
non-Apple targets.
build: correct variable in SDK configuration
…erty wrappers. (swiftlang#32003)

In `Differentiable` derived conformances, determine whether a property-wrapped property is mutable by checking whether a setter exists, instead of calling `VarDecl::getPropertyWrapperMutability()`.

Resolves rdar://63577692 (SR-12873) where class-typed property wrappers with a mutable `wrappedValue` are rejected by synthesis (not included in the `TangentVector`). Also improve the property-wrapper-spe
cific immutability warning message.
@kateinoigakukun kateinoigakukun merged commit 4499dd3 into swiftwasm May 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants