Closed treeowl closed 1 year ago
One option would be to not really use a custom prelude, and just do import Prelude (); import CustomPrelude
everywhere. There are few enough modules to make that a reasonable option. The bogus application is still useful for repl stuff, since it will use the compiled code, but it's probably not ideal if someone wants to use the debugger.
I renamed the custom prelude and got rid of the workaround in #37. It never seems to have worked right anyway; to do that will take a Cabal project, I think.
Running
cabal repl
on the library errors out with a mysterious complaint about the customPrelude
.