Skip to content

[pull] swiftwasm from main #2018

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 6 commits into from
Oct 16, 2020
Merged

[pull] swiftwasm from main #2018

merged 6 commits into from
Oct 16, 2020

Conversation

pull[bot]
Copy link

@pull pull bot commented Oct 16, 2020

See Commits and Changes for more details.


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

aschwaighofer and others added 6 commits October 15, 2020 14:32
Concrete types can conform to unavailable protocols because
the witness table for the conformance is not required for use
with the concrete type itself.

However, protocols cannot have unavailable base protocols.
I believe this was an oversight of the original implementation
here.
…ations

Access control, availability and exportability checking missed these
because of a baked-in assumption that getGenericParams() == nullptr
rules out the presence of a trailing where clause.
This was a no-op and it doesn't make sense in the current model.
…rect_return_results_loadable_by_address

LoadableByAddress: Make sure that indirect return arguments are at the right type expansion
…y-fixes

Small availability checking fixes
@pull pull bot merged commit 691bef6 into swiftwasm Oct 16, 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.

3 participants