Closed FroMage closed 9 years ago
For some other stuff I was working on I fixed some of this almost as if by accident.
The error count will now only count errors like it should.
We also ignore AnalysisMessage
s if we have ParseError
s, just like the JVM backend and the IDE do, so the above list might be less "crowded".
I don't know about pulling up the errors, we don't do that in the JVM backend either. Personally I'd expect errors and warnings that are close in the file to be also close in the output (and you can always simply filter out the warnings).
I don't know what to do about the "ceylon compile-js: 31 errors." being in the middle though, is there some threading going on?
Could the 31 errors in the middle could be due to logging issues? Like, using some logging backend instead of System.out.println
?
No idea, I put a flush()
in there somewhere to see if it helped and I have not been able to reproduce it at least so it might be fixed already.
I can't reproduce this anymore, so let's just consider this closed. Reopen if you still see it @FroMage.
1
, not31
: it should not count warnings