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
this is more a general question - is there a strong reason not to include a hash of the flags (and other relevant configuration) in the cache directory? it's kind of annoying that running a profiling build means rebuilding everything, or adopting a filthy hack like http://www.shimweasel.com/2017/04/27/haskell-profiling-without-pain
even nix doesn't solve this problem for the actual build as far as I'm aware, only for dependencies. Is this something the stack devs think is worth solving? should it be done by another tool?
The text was updated successfully, but these errors were encountered:
this is more a general question - is there a strong reason not to include a hash of the flags (and other relevant configuration) in the cache directory? it's kind of annoying that running a profiling build means rebuilding everything, or adopting a filthy hack like http://www.shimweasel.com/2017/04/27/haskell-profiling-without-pain
even nix doesn't solve this problem for the actual build as far as I'm aware, only for dependencies. Is this something the stack devs think is worth solving? should it be done by another tool?
The text was updated successfully, but these errors were encountered: