Mike Pilgrem

Results 132 comments of Mike Pilgrem

> Have you checked GHC 9.10/Cabal-3.10? As the problem is what different versions of Cabal (the library) are, or are not, passing to GHC, I reason that changing GHC version...

I agree with @mouse07410. I was able to try the GHC 9.10.1/Cabal 3.10.2.0 combination by adding to the Cabal file: ~~~yaml build-type: Custom custom-setup setup-depends: base, Cabal ==3.10.2.0 ~~~ and...

@mouse07410, the official release of Stack 2.15.7 has a dependency on `Cabal=3.10.3.0`, but Stack does not use that dependency to build. For `Simple` it uses the boot package of the...

@mouse07410, yes GHC 9.10.1 comes with Cabal-3.12.0.0. This is a handy source: https://gitlab.haskell.org/ghc/ghc/-/wikis/commentary/libraries/version-history. This is another: https://www.snoyman.com/base/.

On isolating the code, my current assumption is that it is something to do with `Distribution.Simple.GHC.Build.ExtraSources.buildSources`: ~~~haskell buildCSources = buildExtraSources "C Sources" Internal.componentCcGhcOptions ( \c -> do let cFiles =...

If the design choice is as intended, the 'problem' is that the change in the Package Description Format Specification was not documented in the following places: * https://cabal.readthedocs.io/en/3.12/file-format-changelog.html#cabal-version-3-12 * https://cabal.readthedocs.io/en/3.12/cabal-package-description-file.html#pkg-field-executable-main-is...

The history is: * March 2005: GHC 6.4 is released, introducing `Cabal-1.0`. That documents: ~~~text main-is: filename (required) The name of the source file containing the Main module, relative to...

I have opened issue #190 to correspond to proposed solutions. I suspect I'll have to wait for an alpha of GHC 9.16 before I (a Windows user) can test myself....

@andreasabel, if I understand correctly, you would like a data constructor added to `SGR` so that hyperlinks can also be treated a bit like underlining is treated: (a) you 'enable'...

I need to look at `getTerminalSize` more closely, full stop, as something is up with `ansi-terminal-example` on Windows 11, namely: * #182