You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Doing cabal install on large projects can take significant amounts of time. However, build errors of dependencies get aggregated and shown at the end of the build, which is a waste of my time, especially if the error occurred early on.
I would have expected that upon first error, cabal aborts the whole build, presenting that error.
My suggestion is to change the default behaviour in the case of an error to "fail fast", unless there is a good use case, that I am unaware of, for the aggregation behaviour.
If existing cabal users have come to depend on the aggregation, I suggest a new flag --fail-fast or similar.
The text was updated successfully, but these errors were encountered:
Doing
cabal install
on large projects can take significant amounts of time. However, build errors of dependencies get aggregated and shown at the end of the build, which is a waste of my time, especially if the error occurred early on.I would have expected that upon first error, cabal aborts the whole build, presenting that error.
My suggestion is to change the default behaviour in the case of an error to "fail fast", unless there is a good use case, that I am unaware of, for the aggregation behaviour.
If existing cabal users have come to depend on the aggregation, I suggest a new flag
--fail-fast
or similar.The text was updated successfully, but these errors were encountered: