[zlonast]

fix: #2056

I think we can simply redefine the flag, and few people will notice, since it doesn't appear in libraries or executables.

Those who do notice will now use the full flag. As I understand it, these are the people who manually enter flags in the console.

Currently, this is mostly LLM, which makes this change even more valuable for them.

---

Template Α: This PR modifies behaviour or interface

Include the following checklist in your PR:

• Patches conform to the coding conventions.
• Any changes that could be relevant to users have been recorded in the changelog.
  • Is the change significant? If so, remember to add significance: significant in the changelog file.
• The documentation has been updated, if necessary.
• Manual QA notes have been included.
• Tests have been added. (Ask for help if you don’t know how to write them! Ask for an exemption if tests are too complex for too little coverage!)

[jappeace]

looks good.

question: why would you ever set a flag to compile with ghc?

[zlonast]

In general, this simply gives the compiler a choice. In the case of ghc, it is always selected by default. We try not to be tied to a single compiler.

[philderbeast]

Please move the -g short option in the users guide too:

cabal/doc/setup-commands.rst

Line 169 in 5445f14

.. option:: -g, --ghc

cabal/doc/cabal-project-description-file.rst

Lines 1247 to 1249 in 5445f14

	.. cfg-field:: debug-info: boolean | integer [0 .. 3]
	--enable-debug-info[=n]
	--disable-debug-info