Admin message

Due to a large amount of spam we do not allow new users to create repositories, they are "external" users. If you are a new user and want to create a repository, for example for forking GHC, open a new issue on ghc/ghc using the "get-verified" issue template

GHC 9.14 :load ignores ghci command line argument settings for import paths
## Summary `ghci` since ghc `9.14.1` seems to ignore `-i` flags passed as CLI argument. ## Steps to reproduce Create a module in `src/Foo.hs` containing anything. (such as `module Foo where x = 10`). With ghc `9.12.2`: ``` $ ghci -isrc GHCi, version 9.12.2: https://www.haskell.org/ghc/ :? for help ghci> :show paths current working directory: /home/guillaume/test_ghci_import module import search paths: . src ghci> :l Foo [1 of 1] Compiling Foo ( src/Foo.hs, interpreted ) Ok, one module loaded. ghci> ``` It works fine as expected, `Foo` is found when using `:load` according to the import `paths` set by `-i`. However, with ghc `9.14.1`: ``` $ ghci -isrc GHCi, version 9.14.1: https://www.haskell.org/ghc/ :? for help ghci> :show paths current working directory: /home/guillaume/test_ghci_import module import search paths: . src ghci> :l Foo <no location info>: error: [GHC-82272] module ‘Foo’ cannot be found locally Failed, unloaded all modules. ghci> :set -isrc ghci> :show paths current working directory: /home/guillaume/test_ghci_import module import search paths: . src src ghci> :l Foo [1 of 1] Compiling Foo ( src/Foo.hs, interpreted )[interactive-session] Ok, one module loaded. ``` As you can see, `:show paths` shows that `src` is correctly included, however `:load` does not work as expected. However, `:set -isrc` introduces a duplicated entry in `:show paths`, and then `:load` works as expected. ## Expected behavior I would like `:load` to correctly respect import paths as provided in the CLI and to be coherent with what `:show paths` returns. ## Environment * GHC version used: 9.12.2 and `9.14.1`, installed from nixpkgs. Optional: * Operating System: Linux * System Architecture: x86_64
issue