SIL: Thread type expansion context through to function convention apis #31470
Conversation
|
@swift-ci Please test |
|
Build failed |
|
@swift-ci Please test |
|
Build failed |
|
Build failed |
|
@swift-ci Please test |
|
Build failed |
|
Build failed |
This became necessary after recent function type changes that keep substituted generic function types abstract even after substitution to correctly handle automatic opaque result type substitution. Instead of performing the opaque result type substitution as part of substituting the generic args the underlying type will now be reified as part of looking at the parameter/return types which happens as part of the function convention apis. rdar://62560867
aschwaighofer
force-pushed
the
fix_rdar62560867
branch
from
cf325a9
to
147144b
Compare
|
@swift-ci Please test |
|
@swift-ci Please test source compatibility |
|
Build failed |
|
Build failed |
|
@swift-ci Please test os x |
|
Build failed |
|
@swift-ci please test source compatibility debug |
|
@swift-ci Please test |
|
@swift-ci Please test source compatibility |
|
Build failed |
|
Build failed |
|
@swift-ci Please test source compatibility debug |
1 similar comment
|
@swift-ci Please test source compatibility debug |
|
@swift-ci Please test |
|
Build failed |
|
Build failed |
This became necessary after recent function type changes that keep
substituted generic function types abstract even after substitution to
correctly handle automatic opaque result type substitution.
Instead of performing the opaque result type substitution as part of
substituting the generic args the underlying type will now be reified as
part of looking at the parameter/return types which happens as part of
the function convention apis.
rdar://62560867