Closed RyanGlScott closed 7 months ago
Similarly, vty-benchmark
fails to build with GHC 9.2:
$ cabal run vty-benchmark -w ghc-9.2
Build profile: -w ghc-9.2.8 -O1
In order, the following will be built (use -v for more details):
- vty-examples-5.37 (exe:vty-benchmark) (first run)
Preprocessing executable 'vty-benchmark' for vty-examples-5.37..
Building executable 'vty-benchmark' for vty-examples-5.37..
[1 of 5] Compiling BenchImageFuzz ( BenchImageFuzz.hs, /home/ryanscott/Documents/Hacking/Haskell/vty/dist-newstyle/build/x86_64-linux/ghc-9.2.8/vty-examples-5.37/x/vty-benchmark/build/vty-benchmark/vty-benchmark-tmp/BenchImageFuzz.o, /home/ryanscott/Documents/Hacking/Haskell/vty/dist-newstyle/build/x86_64-linux/ghc-9.2.8/vty-examples-5.37/x/vty-benchmark/build/vty-benchmark/vty-benchmark-tmp/BenchImageFuzz.dyn_o )
BenchImageFuzz.hs:22:12: error:
Variable not in scope: mkVty :: VtyUserConfig -> IO Vty
|
22 | vty <- mkVty defaultConfig
| ^^^^^
vty-interactive-terminal-test
was actually moved to vty-crossplatform
and I just forgot to remove it from vty
. I definitely haven't maintained the benchmark program, but either way, it needs to be moved elsewhere to a package that provides mkVty
. I'm inclined to just remove it, but I'll keep this open as a reminder to take a look.
I'm just exploring Vty for the first time and the broken examples/
have caused a fair amount of confusion! I'd definitely encourage you to remove them if there's no prospect of them being fixed in the near future. Thye could always be re-introduced later on.
I went ahead and removed examples
and updated the package description to point to the ones in vty-crossplatform
. Sorry for the confusion!
I tried to run
vty-interactive-terminal-test
recently with GHC 9.2, but it fails to compile: