Home/ Questions/Q 910135
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-15T16:59:37+00:00

Often there’s no need to pay any attention to implicit arguments in Scala, but

  • 0

Often there’s no need to pay any attention to implicit arguments in Scala, but sometimes it’s very helpful to understand how the compiler is automatically providing them. Unfortunately, this understanding seems to be hard to obtain!

Is there a general method to discover how an implicit parameter has been provided, in a given piece of code?

Ideally, one day IDE integration would provide this information in some way, but I expect for now I’ll have to dig deeper. Is there some way to ask the compiler to explain exactly which implicit definition it chooses at any given point? Can this be deciphered indirectly from other compiler output?

As an example, I’d like to know how to work out on my own where the implicit bf: CanBuildFrom[Repr, B, That] argument to TraversableLike.map comes from, without reading questions like this one on Stack Overflow!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team
    1. Add the option -Xprint:typer to the scalac command line. This prints the program tree just after the typer compiler phase. This works best with a short, self contained example. You can also pass this to scalac. This is a really huge step towards self-reliance in Scala!
    2. As mentioned by Randall, IntelliJ shows in-scope and the selected Implicit View with CTRL-ALT-SHIFT-I. Wait a month or two and implicit arguments are likely to have similar support.
    • 0