semantic/script/repl

#!/bin/bash
# Usage: script/repl [ARGS...]
# Run a repl session capable of loading all of the packages and their individual components. Any passed arguments, e.g. module names or flags, will be passed to ghci.

set -e

cd "$(dirname "$0")/.."

# do a build of dependencies up front to ensure they’re all available
cabal v2-build all --enable-benchmarks --enable-tests --only-dependencies

# exec ghci with the appropriate flags, and without the $GHC_ENVIRONMENT variable interfering
cabal v2-exec env -- -u GHC_ENVIRONMENT ghci -ghci-script=.ghci.repl $(script/ghci-flags) -no-ignore-dot-ghci $@
-												Add a script to run ghci.

											
										
										
											2019-10-30 22:18:43 +03:00
+								#!/bin/bash
-												Usage for script/repl.

											
										
										
											2019-10-30 23:08:42 +03:00
+								# Usage: script/repl [ARGS...]
 								# Run a repl session capable of loading all of the packages and their individual components. Any passed arguments, e.g. module names or flags, will be passed to ghci.
-												Add a script to run ghci.

											
										
										
											2019-10-30 22:18:43 +03:00
 								set -e
-												Quote paths when changing directories.

											
										
										
											2019-12-18 17:00:13 +03:00
+								cd "$(dirname "$0")/.."
-												Add a script to run ghci.

											
										
										
											2019-10-30 22:18:43 +03:00
-												Move the cabal build call into script/repl.

Doing it in script/ghci-flags means it has to be silent, which is super confusing/surprising.

Doing it in script/repl means we can see what it’s up to.

											
										
										
											2019-12-20 18:44:02 +03:00
+								# do a build of dependencies up front to ensure they’re all available
-												Build the benchmarks’ dependencies.

											
										
										
											2019-12-20 18:44:28 +03:00
+								cabal v2-build all --enable-benchmarks --enable-tests --only-dependencies
-												Move the cabal build call into script/repl.

Doing it in script/ghci-flags means it has to be silent, which is super confusing/surprising.

Doing it in script/repl means we can see what it’s up to.

											
										
										
											2019-12-20 18:44:02 +03:00
-												:memo: the exec call.

											
										
										
											2019-12-18 17:17:08 +03:00
+								# exec ghci with the appropriate flags, and without the $GHC_ENVIRONMENT variable interfering
-												Disallow customizing the build dir.

											
										
										
											2019-12-18 17:00:23 +03:00
+								cabal v2-exec env -- -u GHC_ENVIRONMENT ghci -ghci-script=.ghci.repl $(script/ghci-flags) -no-ignore-dot-ghci $@