Once we've gained enough experience with the cabal-env prototype we can start merging it into cabal proper. However, I'm not fully satisfied with cabal-env right now; I still need to implement a few more modes and try them out; this is also related to @typedrat's new-install work which implements a small subset of cabal-env for the library-install use-case.
PS: I don't like the cabal global idea to denote forcing a project-less context; My plan was rather to have cabal --project-file='' repl ... (or maybe some sugar flag, cabal --no-project repl ...) tell cabal to ignore any project context (i.e. ignore any cabal.project or *.cabal file in fs-scope).
Sometimes I just need to check a couple of things in GHCi, not specific to any project. I could run
ghci, but then I don't get access to any packages except the ones that are installed globally.
stackI can run
stack ghci --package lens, for instance.
cabalI have to create something like this:
and then run
cabal new-replin a directory with this
I'd prefer to write
cabal new-repl --package lens:
dist-newstylein the current directory, instead it could use
The text was updated successfully, but these errors were encountered: