Make a default-language optional in cabal-version: 3.2 #6288
Milestone
Comments
|
I've been wanting to do this as well; the only thing we need however is to make sure that there's a way to not send any |
|
Is there a way to not-send any -XHaskell* nowadays? Omitting default-language field generates an error, is that wrong?
… On 7 Oct 2019, at 9.09, Herbert Valerio Riedel ***@***.***> wrote:
I've been wanting to do this as well; the only thing we need however is to make sure that there's a way to don't send any -XHaskell2010 at all to GHC (e.g. via an empty default-language: ?)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
SGTM. |
|
+1 |
phadej
added a commit
to phadej/cabal
that referenced
this issue
Jun 22, 2020
phadej
added a commit
to phadej/cabal
that referenced
this issue
Jun 22, 2020
phadej
added a commit
that referenced
this issue
Jun 22, 2020
Add check tests for default-language (#6288)
phadej
added a commit
to phadej/cabal
that referenced
this issue
Jun 22, 2020
- Add availableSince to language/extension fields - Also autogen-modules once we are on that. - Remove default-language check for cabal-version: 3.4 We cannot make the field `uniqueFieldAlaDef`, as that would require specifying `default-language` in each subconditional. I leave it for haskell#6925 Note: the default language is whatever is the compiler's default. The GHC-8.10 default is its variant of Haskell2010 with NondecreasingIndentation and without DatatypeContexts
phadej
added a commit
that referenced
this issue
Jun 23, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It's essentially always
Haskell2010nowadays.We can introduce the same
Defaultthing as we did withbuild-type👍 / 👎 ?
The text was updated successfully, but these errors were encountered: