Don't use tryWithFallback #2493
Merged
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.
Why not?
which can add up
which caused the fallback.
The only test failing after removal was t2429.scala. That test
was originally for an issue where scalac crashed. It involves
some fairly exotic code over List[Nothing]'s. I think we can
ignore it for now, and just add the type annotation to make it
compile.
The commit also contains some improvements for implicit search diagnostics and a test that was used to find the issues. Originally the goal was to get better info out of -explain-implicits. That's still unfulfilled, but at least the search does not become weird anymore. Previously, instead of getting an "implicit not found" error we got a an ambiguous implicit because the fallback tried again with a wildcard expected type.