val test = 1
1.flatMap{_.toString} // error
val list = List(1,2,3) // hover cursor over "list", no type info
Silly example, but you get the point:
val test = 1
1.flatMap{_.toString} // error
val list = List(1,2,3) // hover cursor over "list", no type info
displays
In fact, no type information displays anywhere in the source file
until error(s) are resolved.
Juno, Java 7, Scala IDE latest (yesterday's nightly)
Am curious to know if others are experiencing the same...
On Oct 21, 3:17 pm, Simon Schäfer <m...@antoras.de> wrote:
> Can you provide a code example to show what is not working? I can't
> follow your text in detail.
>
> On Sun 21 Oct 2012 02:22:41 PM CEST, virtualeyes wrote:
>
>
>
>
>
>
>
> > This may be a difficult problem to solve, but one event that annoys me
> > daily is, while hacking out some test code block (e.g. to figure out
> > why another piece of code is not working), type inference (that is,
> > hover cursor over class/property/method and see type information)
> > vanishes, and I then have to comment out/get working any errors in the
> > source file before type inference returns (sometimes I have to close/
> > re-open the file)
>
> > If this is a Juno issue let me know. Also, if it's just the way it is,
> > let me know, can live with it ;-)
It can actually happen without errors as well (although errors in
source file will effectively guarantee it)
Code ahead, type inference, everything goes.
I then have to project clean and/or close & re-open the source file
before I can escape from blind coding.
Could be a Juno issue, I have no clue, just pointing it out.
If everyone else has rock solid consistent code ahead + type
inference, count me as envious...
No, 2.9.2
Outline view is fine.
Could be Juno, could be incremental builds with Play 2 Scala, SBT...
I'll setup Indigo when I get the chance and see what the performance
differences are...
Thanks (semantic highlighting works great, btw, hung thread issue
seems to be gone ;-))