Imported From: https://issues.scala-lang.org/browse/SI-2206?orig=1
Reporter: @stepancheg

@paulp said:
I tend to agree that this is a bug, because given the import statement, the implicit should be made available -- however in case you are unaware, in general implicits which lexically follow the point at which you want them to work need an explicit return type to be considered. And this example does work if you supply it.

  implicit def ax(a: A): AX = new AX

@TiarkRompf said:
Paul, can you have a look if it's possible to generate a better error message?

@paulp said:
Replying to [comment:3 rompf]:

Paul, can you have a look if it's possible to generate a better error message?

I probably wasn't clear in my first comment - in order to generate a better error message I need to understand why it's an error. I would have expected that explicitly importing the contents of an object, regardless of the location of that object, means that the implicits inside the object would now be eligible for statements following the import. As that is not the case, I'm not sure what the message would say.

It would certainly be nice though if when there is a type error, and the compiler has some knowledge of an ineligible implicit that would have made the error go away, if it would tell you both the implicit and why it wasn't used.

@paulp said:
I'm throwing this back to scala_reviewer as I can't do anything with it without knowing what we think should happen, or if it's an error, why it's an error. As I said above, I agree with the submitter that this code should compile.

@odersky said:
I don't think it's possible to compile this. The problem is that we have to be very careful which implicits to evaluate, for fear of falling into infinite cycles. So the best thing we could do is give a better error message. I'm reassgning back to you, Paul, but I'm also happy if you turn it into a won't fix subsequently.

@paulp said:
It's funny, it turns out the error message was in there all along, but not being printed due to a logic error. I fixed it mostly by accident working on other error messages. I'll close this as soon as I check it in.

@paulp said:
Explanatory error in trunk as of r21706.