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
In general, if I'm debugging a GHC problem, I get Cabal to spit out the command line I need, and then call GHC myself. If I'm debugging a Cabal problem, I don't really care about what GHC is doing except at broad strokes (black box.) So let's stop passing -v to GHC when Cabal's verbosity is sufficiently high.
The text was updated successfully, but these errors were encountered:
In general, if I'm debugging a GHC problem, I get Cabal to spit out the command line I need, and then call GHC myself. If I'm debugging a Cabal problem, I don't really care about what GHC is doing except at broad strokes (black box.) So let's stop passing
-v
to GHC when Cabal's verbosity is sufficiently high.The text was updated successfully, but these errors were encountered: