Skip to content

Better error messages for extension methods, showing "overloaded" alternatives (when implicit search fails) #7906

Open
@scabug

Description

@scabug

work-in progress:
Many libraries like Slick and shapeless make extensive use of implicit-driven method extensions for types. When implicit search fails error messages could be much more helpful. Ideally, users should be supported in detecting and correcting:

  1. providing wrong arguments to an (extension) method
  2. passing valid arguments to an existing (extension) method which a requires an implicit that cannot be found
    This could probably be done by letting implicit search keep a list of methods that were found because the name matched but neglected due to wrong arguments and missing implicits. The list could be displayed to the user similar to showing overloads in case of an error.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions