Smarter code completion on import clause for module's methods
Code completion should be smarter when used for importing a module's method.
Let's say you have the following
And you want to use Foo.doSmthWith in
The completed import will be import Foo.doSmthWith(f), while it should be import Foo.doSmthWith.
Let's say you have the following
//Foo.scala
object Foo {
doSmthWith(that: Any)(f: Any => Unit): Unit = ()
}
And you want to use Foo.doSmthWith in
//Bar.scala
import Foo.doSmth /*<ask code completion here>*/
object Bar {
doSmthWith(new Object) { _ => () }
}
The completed import will be import Foo.doSmthWith(f), while it should be import Foo.doSmthWith.
Leave a comment
on 2012-07-01 16:00 *
By Mirco Dotta
Summary changed from Smarter code completion on import clause for methods to Smarter code completion on import clause for module's methods
on 2013-09-09 16:18 *
By Mirco Dotta
Version changed from 2.1.0-nightly-29 to 3.0.1-210
Milestone changed from Backlog to Sprint
on 2013-09-23 17:29 *
By Mirco Dotta
In scala-ide:296e54ca7d5e1a6e1a79e907b80c0453a6b2afa0 Don't add parameter list on import completion for module's methods