Fix 2.13.7 regression in implicit resolution #9829
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When implicits are disabled, we can't recover later with a conversion. Esp. when we are already type checking an implicit conversion. This fixes a regression uncovered in Finch.
SethTisue
added
the
prio:blocker
SethTisue
added
release-notes
SethTisue
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Tweak inferMethodInstance to consider if implicits are enabled
When implicits are disabled, we can't recover later with a conversion.
Esp. when we are already type checking an implicit conversion.
This fixes a regression uncovered in Finch: finagle/finch#1417
Unfortunately I don't have a minimal reproduction for a test.
I guess adding Finch to the community build might be a good idea: scala/community-build#1504