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
I think, it is pretty normal to use haskell.nix on the CI, and also it is a good idea to have -Werror on the CI, but only for local (project) packages. Stack supports this by allowing one to set options on a fake package called $local, but, arguably, stack.yaml is not the right place to have this, since during development you don’t actually want to have -Werror.
In haskell.nix it feels like some combination of modules on e.g. stackProject and haskellLib.selectProjectPackages could do the trick, but this is, obviously, a very bad idea and won’t work because of recursion. The problem is that we need to have the result of stackProject to get at list of local packages, but then what we want to craft based on this output is actually one of the inputs of the function.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I think, it is pretty normal to use haskell.nix on the CI, and also it is a good idea to have
-Werror
on the CI, but only for local (project) packages. Stack supports this by allowing one to set options on a fake package called$local
, but, arguably,stack.yaml
is not the right place to have this, since during development you don’t actually want to have-Werror
.In haskell.nix it feels like some combination of
modules
on e.g.stackProject
andhaskellLib.selectProjectPackages
could do the trick, but this is, obviously, a very bad idea and won’t work because of recursion. The problem is that we need to have the result ofstackProject
to get at list of local packages, but then what we want to craft based on this output is actually one of the inputs of the function.Prior art:
ghcOptions
on all packages at once, but that is too much.The text was updated successfully, but these errors were encountered: