Re: Factors that prevent implicit conversions to be found
Simon Schäfer <[email protected]>
| Newsgroups | gmane.comp.lang.scala |
|---|---|
| Message-ID | <[email protected]> |
On 05/22/2015 09:09 AM, Johannes Rudolph wrote: > Thanks again Martin, the missing result types were exactly the > problem. I guess this also explains the sometimes observed > non-deterministic cases where the order of compilation units during > incremental were another factor that would allow the compilation to > succeed in a few cases. Actually I thought the compiler is already emitting a warning in such cases but after looking at the corresponding ticket https://issues.scala-lang.org/browse/SI-5265 it doesn't seem to be implemented yet. I must have dreamed it - or I used another linting tool that supports the functionality. > > Johannes > > On Thu, May 21, 2015 at 5:31 PM, Johannes Rudolph > <[email protected]> wrote: >> On Thu, May 21, 2015 at 5:27 PM, martin odersky <[email protected]> wrote: >>> Could it be a case of an implicit with a missing result type? >> Ah, yes, that could be. It's a path-dependent result type, so it >> wasn't spelled out. I'll see what happens if it is spelled out. >> >> Thanks, >> >> -- >> Johannes >> >> ----------------------------------------------- >> Johannes Rudolph >> http://virtual-void.net > > -- You received this message because you are subscribed to the Google Groups "scala-language" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.