Merge nested polytypes in more cases in resolveOverloaded #15636
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In some cases while going deeper into alternatives during overload resolution,
we may end up with a nested polytype after dropping contextual parameters.
In particular this can happen for an extension with a
using
clause, as seenin tests/pos/i11713.scala and tests/pos/i13668.scala.
The overload applicability test fails here unless the type parameter lists
are merged.
Co-authored-by: Gagandeep Kalra gagandeepkalra1994@gmail.com
Co-authored-by: Mark T. Kennedy mtk@acm.org
Fixes #11713
Fixes #13668