Skip to content

Conversation

@xedin
Copy link
Contributor

@xedin xedin commented Aug 13, 2025

… into context

Parameter type could be represented by an associated type which is bound to a concrete type by an extension, AbstractFunction::getType() should map it into context before returning because the construct is that it always produces a function type.

Resolves: rdar://156955193

@xedin xedin requested a review from DougGregor August 13, 2025 00:16
… into context

Parameter type could be represented by an associated type which is
bound to a concrete type by an extension, `AbstractFunction::getType()`
should map it into context before returning because the construct is
that it always produces a function type.

Resolves: rdar://156955193
@xedin
Copy link
Contributor Author

xedin commented Aug 13, 2025

@swift-ci please test

@xedin
Copy link
Contributor Author

xedin commented Aug 13, 2025

@swift-ci please test Linux platform

@xedin
Copy link
Contributor Author

xedin commented Aug 13, 2025

@swift-ci please smoke test Linux platform

@xedin
Copy link
Contributor Author

xedin commented Aug 13, 2025

@swift-ci please test Linux platform

@xedin xedin merged commit 1060643 into swiftlang:main Aug 13, 2025
5 checks passed
xedin added a commit that referenced this pull request Aug 28, 2025
… mapped… (#83954)

… into context

- Explanation:

Parameter type could be represented by an associated type which is bound
to a concrete type by an extension, `AbstractFunction::getType()` should
map it into context before returning because the construct is that it
always produces a function type.

- Resolves: rdar://156955193

- Main Branch PR: #83687

- Risk: Low. This is a very narrow fix that only affects situations when
parameter type, represented by an associated type, is bound by an
extension.

- Reviewed By: @DougGregor 

- Testing: Added new test-cases to the suite.

(cherry picked from commit 32b97d0)
(cherry picked from commit 7f65291)

<!--
If this pull request is targeting a release branch, please fill out the
following form:

https://github.com/swiftlang/.github/blob/main/PULL_REQUEST_TEMPLATE/release.md?plain=1

Otherwise, replace this comment with a description of your changes and
rationale. Provide links to external references/discussions if
appropriate.
If this pull request resolves any GitHub issues, link them like so:

  Resolves <link to issue>, resolves <link to another issue>.

For more information about linking a pull request to an issue, see:

https://docs.github.com/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue
-->

<!--
Before merging this pull request, you must run the Swift continuous
integration tests.
For information about triggering CI builds via @swift-ci, see:

https://github.com/apple/swift/blob/main/docs/ContinuousIntegration.md#swift-ci

Thank you for your contribution to Swift!
-->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants