Closed
Description
Currently, we're using the base-noprelude trick for a custom prelude. But since cabal-2.2 it's possible to use the mixins approach for this purpose which has the following advantages:
- No extra dependency in a generated project
- Simpler
stack.yamlfile - No
other-modulesvsexposed-modulesdilemma
Since we're planning to use 2.4 by default and since stack supports this approach, let's use a more convenient way of enabling alternative preludes.