Skip to content

[pull] swiftwasm from main #1922

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 4 commits into from
Oct 5, 2020
Merged

[pull] swiftwasm from main #1922

merged 4 commits into from
Oct 5, 2020

Conversation

pull[bot]
Copy link

@pull pull bot commented Oct 5, 2020

See Commits and Changes for more details.


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

xwu and others added 4 commits September 11, 2020 09:56
…d of TypeBase's hasOpaqueArchetypePropertiesOrCases

A type is IsTypeExpansionSensitive if it contains an opaque result type that influences how the type is lowered.

This could be because the type mentions an opaque archetype and
therefore we would look through to the underlying type depending on the
type expansion and could get a different SIL type. For example
'() -> out some P' could lower to '() -> @out Int'.

Or this could be because when we lower an aggregate type some of its
fields are opaque types that could be looked through and therefore the
aggregate has different lowering (e.g address vs. loadable) in different
type expansion contexts.

By replacing it this change also fixes an infinite recursion in
hasOpaqueArchetypePropertiesOrCases.

rdar://68798822
…chetypePropertiesOrCases

Fix TypeBase::hasOpaqueArchetypePropertiesOrCases for recursive types
…s-a-wonderful-source-of-cheerfulness

[stdlib] Simplify 'BinaryFloatingPoint.init?<T: BinaryFloatingPoint>(exactly: T)'
@pull pull bot merged commit 235f401 into swiftwasm Oct 5, 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