GHC issueshttps://gitlab.haskell.org/ghc/ghc/-/issues2019-07-07T18:14:31Zhttps://gitlab.haskell.org/ghc/ghc/-/issues/15055ghci - improve error on hidden package2019-07-07T18:14:31ZAlexander Kjeldaasghci - improve error on hidden packageA user boldly types:
```
> import Data.Foo
<no location info>: error:
Could not find module ‘Data.Foo’
It is a member of the hidden package ‘package-foo-0.1.0.0@package-foo-0.1.0.0-5Itxx5SAgKEAspB2MHVKqi’.
```
The above error ...A user boldly types:
```
> import Data.Foo
<no location info>: error:
Could not find module ‘Data.Foo’
It is a member of the hidden package ‘package-foo-0.1.0.0@package-foo-0.1.0.0-5Itxx5SAgKEAspB2MHVKqi’.
```
The above error message is rather useless for a newcomer to ghci. After lots of googling, the user figures that `:set -v -package package-foo` seems to solve it.
The original error should be:
```
> import Data.Foo
<no location info>: error:
Could not find module ‘Data.Foo’
It is a member of the hidden package ‘package-foo-0.1.0.0@package-foo-0.1.0.0-5Itxx5SAgKEAspB2MHVKqi’.
Try :set -package package-foo to make it visible.
```
Or something like that.
<details><summary>Trac metadata</summary>
| Trac field | Value |
| ---------------------- | ------------ |
| Version | 8.2.2 |
| Type | Bug |
| TypeOfFailure | OtherFailure |
| Priority | normal |
| Resolution | Unresolved |
| Component | GHCi |
| Test case | |
| Differential revisions | |
| BlockedBy | |
| Related | |
| Blocking | |
| CC | |
| Operating system | |
| Architecture | |
</details>
<!-- {"blocked_by":[],"summary":"ghci - improve error on hidden package","status":"New","operating_system":"","component":"GHCi","related":[],"milestone":"8.6.1","resolution":"Unresolved","owner":{"tag":"Unowned"},"version":"8.2.2","keywords":[],"differentials":[],"test_case":"","architecture":"","cc":[""],"type":"Bug","description":"A user boldly types:\r\n\r\n{{{\r\n> import Data.Foo\r\n\r\n<no location info>: error:\r\n Could not find module ‘Data.Foo’\r\n It is a member of the hidden package ‘package-foo-0.1.0.0@package-foo-0.1.0.0-5Itxx5SAgKEAspB2MHVKqi’.\r\n}}}\r\n\r\nThe above error message is rather useless for a newcomer to ghci. After lots of googling, the user figures that `:set -v -package package-foo` seems to solve it.\r\n\r\nThe original error should be:\r\n\r\n{{{\r\n> import Data.Foo\r\n\r\n<no location info>: error:\r\n Could not find module ‘Data.Foo’\r\n It is a member of the hidden package ‘package-foo-0.1.0.0@package-foo-0.1.0.0-5Itxx5SAgKEAspB2MHVKqi’.\r\nTry :set -package package-foo to make it visible.\r\n}}}\r\n\r\nOr something like that.","type_of_failure":"OtherFailure","blocking":[]} -->8.6.1Chaitanya Koparkarckoparkar@gmail.comChaitanya Koparkarckoparkar@gmail.comhttps://gitlab.haskell.org/ghc/ghc/-/issues/13896Use response file to invoke hsc2hs2019-07-07T18:19:36ZBen GamariUse response file to invoke hsc2hsWe already use response files when invoking Haddock due to Windows command line length limitations. It [seems](https://github.com/haskell/cabal/issues/3122#issuecomment-311489312) that we also need to do the same with `hsc2hs`.
<details...We already use response files when invoking Haddock due to Windows command line length limitations. It [seems](https://github.com/haskell/cabal/issues/3122#issuecomment-311489312) that we also need to do the same with `hsc2hs`.
<details><summary>Trac metadata</summary>
| Trac field | Value |
| ---------------------- | ------------ |
| Version | 8.0.1 |
| Type | Bug |
| TypeOfFailure | OtherFailure |
| Priority | high |
| Resolution | Unresolved |
| Component | hsc2hs |
| Test case | |
| Differential revisions | |
| BlockedBy | |
| Related | |
| Blocking | |
| CC | |
| Operating system | |
| Architecture | |
</details>
<!-- {"blocked_by":[],"summary":"Use response file to invoke hsc2hs","status":"New","operating_system":"","component":"hsc2hs","related":[],"milestone":"8.4.1","resolution":"Unresolved","owner":{"tag":"Unowned"},"version":"8.0.1","keywords":[],"differentials":[],"test_case":"","architecture":"","cc":[""],"type":"Bug","description":"We already use response files when invoking Haddock due to Windows command line length limitations. It [[https://github.com/haskell/cabal/issues/3122#issuecomment-311489312|seems]] that we also need to do the same with `hsc2hs`.","type_of_failure":"OtherFailure","blocking":[]} -->8.6.1Chaitanya Koparkarckoparkar@gmail.comChaitanya Koparkarckoparkar@gmail.com