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
Calling "stack build" currently doesn't report the files that are being processed by build-tools such as happy and alex.
When multiple files are processed by build-tools,
it is no longer clear to which file the reported errors and/or warnings belong.
Could the files being processed by build-tools be echoed,
such that it becomes clear to which file a message belongs?
To give an example:
I prefer
alex sys/front/TxsAlex.x
alex sys/smt/RegexAlex.x
alex sys/smt/SMTAlex.x
alex sys/smt/SMTStringAlex.x
happy sys/front/TxsHappy.y
unused rules: 4
unused terminals: 3
happy sys/smt/RegexPosixHappy.y
happy sys/smt/RegexSMTHappy.y
shift/reduce conflicts: 15
happy sys/smt/SMTHappy.y
happy sys/smt/SMTStringHappy.y
Yes, this should be easy to do by modifying preprocessFile. Hardest thing is deciding exactly what we want output, at what verbosity. Your suggestion is to print just the preprocessor name and file name (NO flags), but this is a bit difficult because the PreProcessor struct doesn't record the name of the preprocessor (nor can we easily add it without breaking Custom setup compatibility.) What if we printed the actual command that was run? Or how about just the filename? (Preprocessing foo/Alex.x)? But maybe this is a bit chatty; perhaps you don't want to see the output if there is no change/output?
Since, in my case, the output is analyzed automatically, I don't mind a chatty output.
Yet, I can understand that some user only want the actual command that was run in case there was output.
For me, the crucial requirement is to be able to determine to which command the output belongs, when output occurs.
Calling "stack build" currently doesn't report the files that are being processed by build-tools such as happy and alex.
When multiple files are processed by build-tools,
it is no longer clear to which file the reported errors and/or warnings belong.
Could the files being processed by build-tools be echoed,
such that it becomes clear to which file a message belongs?
To give an example:
I prefer
over the current output
According to the stack developers (see
commercialhaskell/stack#2843 (comment))
this is a cabal issue!
The text was updated successfully, but these errors were encountered: