Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Backport "Bring back ambiguity filter when we report an implicit not found error" to LTS #21103

Merged
merged 2 commits into from
Jul 6, 2024
Merged

Backport "Bring back ambiguity filter when we report an implicit not found error" to LTS #21103

merged 2 commits into from
Jul 6, 2024

Commits on Jul 6, 2024

  1. Bring back ambiguity filter when we report an implicit not found error 

    This reverts one part of #20261. When we fail with both an ambiguity on one implicit argument and another error on another argument we prefer the other error. I added a comment why this is needed.

Fixes #20344

[Cherry-picked 863077c]
    @odersky @WojciechMazur
    odersky authored and WojciechMazur committed Jul 6, 2024
    Configuration menu
    Copy the full SHA
    d33a968 View commit details
    Browse the repository at this point in the history

  2. Update compiler/src/dotty/tools/dotc/typer/Typer.scala 

    Co-authored-by: Matt Bovel <matthieu@bovel.net>
[Cherry-picked 783b7bd]
    @odersky @WojciechMazur
    odersky authored and WojciechMazur committed Jul 6, 2024
    Configuration menu
    Copy the full SHA
    1ee9297 View commit details
    Browse the repository at this point in the history