Michał Pałka

I would argue that it's correct that `StringBufferInputStream` is missing - it's not in scope by default unless you import it, e.g. ```scala object A { val a: StringBufferInputStream =...

I'm not sure if it really makes sense to filter out objects without members. Actually for true scala objects you always have `.type` as a possible member. For java types...

We need objects with `.type` as the only type members because something like `Foo.type` might actually be what the user wanted to type. In case of `trait`s and `type`s that...

I'm afraid there are no flags on a class indicating if it has any nested type members. But if you have a symbol and you know it's a class you...

OK, I finally managed to reproduce the issue myself too. To me it looks like the problem is somehow connected with the fact that the class loader used by the...

A small rectification: It seems it's not about what you evaluate before but whether there is only one completion suggestion or more. So there will be no error after completing...

The error is correct. I think you have simply misunderstood how context functions work. The compiler complains about the lack of a defined given instance of type `Int` which you...

But in your particular case how in your opinion should the compiler know that ``` provide2(implicitly[String] + implicitly[Int]) ``` should be e.g. ``` provide2[String, Int, String](implicitly[String] + implicitly[Int]) ``` (which...

So you would expect that ``` provide2 { val s = implicitly[String] val i = implicitly[Int] s + i } ``` would return a `(String, Int) => String` but ```...

On the other hand, while the ordering of arguments is important for ordinary functions, for context functions the difference between `(String, Int) ?=> String` and `(Int, String) ?=> String` is...