haskell / haskell/cabal

Reconsider warning about missing languages

Open
#11,025 2 comments 0 reactions 0 assignees View on GitHub
cabal-install: cmd/check type: discussion
Dominant language
Haskell
Stars
1.7k
Forks
750
Avg merge
4d 3h
Merged PRs (30d)
28

Description

> It's a curious problem. The GHC* "languages" will multiply in the future (iiuc GHC SC's current intentions). So, simply two branches (if/else) won't be enough soon. I'm wondering if we should support something like `default-language: GHC` which would mean the latest supported GHC*.
>
> Semantically, saying "give me the latest GHC language that this compiler supports" comes dangerously close to not specifying a language — the very situation `cabal check` was supposed to flag. But I think this idea behind the check hasn't aged well (due to invention of GHC* "languages") and we should revisit it.

_Originally posted by @ulysses4ever in [#11017](https://github.com/haskell/cabal/issues/11017#issuecomment-3004574096)_.

Consider also what @tonyday567 is doing in #11017, abstracting away/backporting language extensions so they are usable to older GHCs. It is a valid usecase.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.