Imported From: https://issues.scala-lang.org/browse/SI-9729?orig=1
Reporter: Felix Dietze (man)

@som-snytt said:
What a great idea. I'm currently doing the scroll dance. Alternatively, an option to limit error output. Both goals are achievable with a custom reporter.

Maybe we could change the priority from "trivial" to "life-changing".

Richard Bradley (richard.bradley) said (edited on Jan 25, 2017 10:44:47 AM UTC):
This sounds like an sbt feature to me, rather than a scalac feature.

This is also a little risky -- to print the errors in reverse order, you'd have to buffer them all in memory until the compile run finished. If the process crashed or was killed, then you'd lose all diagnostic info. The current approach of printing errors as soon as they occur at least means that the compiler can be killed without losing info if the user doesn't want to wait for the run to finish.

@som-snytt said (edited on Jan 25, 2017 6:29:02 PM UTC):
There's also -Xprompt.

Another idea is a reporter that summarizes with: "The first error was...".

@som-snytt said (edited by @lrytz on Feb 3, 2017 3:45:04 PM UTC):
scala/scala#5667 introduces -Xmaxerrs / -Xmaxwarns

@SethTisue said:
I agree with Richard's comments. And in general, I'm leery of trying to please all people with a proliferation of compiler options for having it your own way, each one seems like a good idea, but the maintenance burden, doc burden, mental "what flags am I running under?" burden, downstream tooling needing to adjust burden, etc – all of this piles up.

Andrew's improvement (now merged!) is a nice one, especially given the javac precedent.

@SethTisue said:
Thinking about ways of addressing the underlying issue here would make an interesting thread on contributors.scala-lang.org, maybe one or more further tickets and/or PRs would come out of it.