[type-classes] Fix issue with type class op resolution inside speculative attribution #1981
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.
During speculative attribution of lambda expressions, we might get to the unary/binary op resolution code with erroneous types.
When this happens, type class witness resolution fails if Numerical/Integral are tweaked to contain witness methods.
This PR fixes this condition and adds a test.
Progress
Reviewers without OpenJDK IDs
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/valhalla.git pull/1981/head:pull/1981$ git checkout pull/1981Update a local copy of the PR:
$ git checkout pull/1981$ git pull https://git.openjdk.org/valhalla.git pull/1981/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 1981View PR using the GUI difftool:
$ git pr show -t 1981Using diff file
Download this PR as a diff file:
https://git.openjdk.org/valhalla/pull/1981.diff
Using Webrev
Link to Webrev Comment