New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
option to reverse the order of compile error messages #9729
Comments
Imported From: https://issues.scala-lang.org/browse/SI-9729?orig=1 |
@som-snytt said: 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 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): 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): |
@SethTisue said: Andrew's improvement (now merged!) is a nice one, especially given the javac precedent. |
@SethTisue said: |
I just had this idea while scrolling upwards in my terminal to find the first compile error:
It would be nice to have the option to print the compile errors in reverse order, then one sees the most relevant error at a first glance. This would be especially helpful when using sbt ~compile.
The text was updated successfully, but these errors were encountered: