For example, the main way to setup relude is:
(in the form of Cabal specification):
mixins:
base hiding (Prelude)
, relude (Relude as Prelude)
, relude
Full example:
build-depends:
base
, relude
mixins:
base hiding (Prelude)
, relude (Relude as Prelude)
, relude
HPack allows to:
- name: base
mixin:
- hiding (Prelude)
- name: relude
mixin:
- (Relude as Prelude)
But into Cabal it gets translated as:
build-depends:
- relude
mixins:
base hiding (Prelude)
, relude (Relude as Prelude)
Which has unexpected behavior - any modules except main Relude module from the tree of relude modules can not be imported.
If only there was a documented way, or if I knew the way to do something like:
- name: base
mixin:
- hiding (Prelude)
- name: relude
mixin:
- (Relude as Prelude)
-
# (or)
- relude
# (or)
- mixin
To put that - relude the second time - it all seems to work fine then if that gets possible.
For example, the main way to setup
reludeis:(in the form of Cabal specification):
mixins: base hiding (Prelude) , relude (Relude as Prelude) , reludeFull example:
HPack allows to:
But into Cabal it gets translated as:
Which has unexpected behavior - any modules except main
Reludemodule from the tree ofreludemodules can not be imported.If only there was a documented way, or if I knew the way to do something like:
To put that
- reludethe second time - it all seems to work fine then if that gets possible.