Clearly, more elaboration is in order, but the Scala plug-in for IDEA is consistent in its basic behavior and features with Scala's Java support, it's just not had several years to mature the way its Java support has.
The framework is still being laid for some of these features. Control Flow Analysis has recently been added. This finds dead code, and lays the basis for Extract Method refactoring which is next. Display of some errors before compilation is currently disabled as there are too many false errors because the type inference is still a little buggy.
No, not even close. Sorry, but that's the truth. It's particularly poor at pointing out many common sources of compiler errors (undefined identifiers, identifiers with the wrong type, etc).
Now admittedly, it's much better than nothing but it's still light years from meeting even the standards that IDEA version 3 set (first version that I used).
Clearly, more elaboration is in order, but the Scala plug-in for IDEA is consistent in its basic behavior and features with Scala's Java support, it's just not had several years to mature the way its Java support has.
is there a plan what feature will be implemented when, in what order, a rough roadmap? i'm planning to use scala for my future projects because the language is so awesome but i'd need at least stable support for the basic features i use the most (error highlighting, extract method, introduce variable (buggy) quickfixes like "create method" and "change signature")
which ide is the best to use for scala development right now? netbeans? eclipse? i might as well take a look at them until jetbrains has caught up
Does it not already do all those things?
Clearly, more elaboration is in order, but the Scala plug-in for IDEA is consistent in its basic behavior and features with Scala's Java support, it's just not had several years to mature the way its Java support has.
Randall Schulz
The framework is still being laid for some of these features. Control Flow Analysis has recently been added. This finds dead code, and lays the basis for Extract Method refactoring which is next. Display of some errors before compilation is currently disabled as there are too many false errors because the type inference is still a little buggy.
-jason
I'm happy to say that there has been a steady stream of type inference fixes, so the plugin is improving in that regard as well.
Randall Schulz wrote:
No, not even close. Sorry, but that's the truth. It's particularly poor
at pointing out many common sources of compiler errors (undefined
identifiers, identifiers with the wrong type, etc).
Now admittedly, it's much better than nothing but it's still light years
from meeting even the standards that IDEA version 3 set (first version
that I used).
is there a plan what feature will be implemented when, in what order, a rough roadmap? i'm planning to use scala for my future projects because the language is so awesome
but i'd need at least stable support for the basic features i use the most (error highlighting, extract method, introduce variable (buggy) quickfixes like "create method" and "change signature")
which ide is the best to use for scala development right now? netbeans? eclipse? i might as well take a look at them until jetbrains has caught up