Can't convert a function to a trait using an implicit conversion and fully structural types #12609 [ci: last-only] #10065
Conversation
This file contains hidden or 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
added 4 commits
June 30, 2022 18:24
…e used instead by the type inference engine
added 6 commits
July 1, 2022 04:30
…y the type inference engine when an unwrapped type is checked.
…y the type inference engine when an unwrapped type is checked.
hunterpayne
changed the title
|
replaced by #10067 |
This pull request was closed.
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.
Attempt to fix 12609 by allowing types without basetypes to be used by the type inference engine when an unwrapped type is checked.
Fixes scala/bug#12609