Skip to content

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Mar 31, 2025

The motivation is the discussion at this Stack issue:

where a user wanted to use Foo.hs containing Foo.main and expected Cabal's main-is field to interpret that.

Explains the use of GHC's -main-is option in Cabal files, when the usual convention of Main.main is not being followed.

This PR does not modify behaviour or interface

  • Patches conform to the coding conventions.
    Not applicable, but style of surrounding text is followed.
  • Is this a PR that fixes CI? If so, it will need to be backported to older cabal release branches (ask maintainers for directions).
    Not applicable.

This is an automatic backport of pull request #10833 done by [Mergify](https://mergify.com).

Explains the use of GHC's `-main-is` option in Cabal files, when the usual convention of `Main.main` is not being followed.

(cherry picked from commit f2d9098)
@Mikolaj Mikolaj added the merge me Tell Mergify Bot to merge label Mar 31, 2025
@mergify mergify bot added the backport label Mar 31, 2025
@mergify mergify bot merged commit 93144da into 3.14 Mar 31, 2025
58 checks passed
@mergify mergify bot deleted the mergify/bp/3.14/pr-10833 branch March 31, 2025 13:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport merge me Tell Mergify Bot to merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants