Re: Factors that prevent implicit conversions to be found
Johannes Rudolph <[email protected]>
| Newsgroups | gmane.comp.lang.scala |
|---|---|
| Message-ID | <CAKF7HndTV7QrGh2HbjiDFp7Ygr3CQwyhWNvmJyPRgw9TM0wXhQ@mail.gmail.com> |
On Fri, May 22, 2015 at 9:50 AM, Simon Schäfer <[email protected]> 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. It seems there are several "levels" of possible conditions. In one case the compiler is able to show you the message, in this case, however, it didn't even detect that it should have looked there. If you take the error message for granted the second condition is at least a bug of error reporting then. The case in question was here btw: https://github.com/akka/akka/pull/17552/files -- 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.