Skip to content

Paths module can get in the way of cabal mixins

Summary

The auto generated Paths module depends on the Prelude that is implicitly imported. This causes issues when e.g. using cabal mixins. Ideally the content of the module should always be the same and not depend on implicitly imported modules.

I think this could be fixed by importing it everything fully qualified.

Steps to reproduce

Add a cabal mixin to your cabal file that e g exports getEnv, this will clash

Expected behavior

The autogenerated Paths module should always compile the same, no matter what env it is in

Environment

  • GHC version used: 9.2

Optional:

  • Operating System: nixos 23.11
  • System Architecture: x86_64-linux
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information