Added or expanded 5 comments…

[liamzee]

…I documented lightly defaultMainHelper in Cabal/Distribution.Simple, expandResponse in Cabal/Distribution.Compat.ResponseFile, expanding the main comment in cabal-install/Distribution.Client.Main, adding segmentation commenting marking responseFiles handling in cabal-install/Distribution.Client.Main (main), added haddock documentation to mainWorker in cabal-install/Distribution.Client.Main .

• Patches conform to the coding conventions.

[ffaf1]

@liamzee , I see closed PRs with similar name, remember you can open one, wait for CI to finish and then update it (push with --force).

Is fourmolu pestering you? Check this bit of CONTRIBUTING.md.

If you need more help, just ask!

[liamzee]

I know the implicit issue, i.e, some maintainers have e-mail alerts set to any attempt at PR, and I just spammed multiple people's inboxes, and I'm really sorry about that.

make style is apparently going berserk, but I'm not going to ask for people's time when I can't even get my fourmolu working on VSC (It's apparently either ignoring the fourmolu.yaml or just diverting to a different piece of software).

Hope that something at least useful comes out of this PR.

[ffaf1]

I know the implicit issue, i.e, some maintainers have e-mail alerts set to any attempt at PR, and I just spammed multiple people's inboxes, and I'm really sorry about that.

Contributions are always appreciated, helping each other is paramount!

fourmolu CI check passed, well done.

[ffaf1]

Commit message should be formatted to standard way, as per CONTRIBUTING.md. Something like

Improve documentation

Add/expalnd comments for functions `defaultMainHelper`, `expandResponse`,
`responseFiles`, `mainWorker`, and for  `Distribution.Client.Main` module.

will do.

[liamzee]

What would you recommend as a path of action, then?

Step 1. Edit the commit message to match requirements; i.e, split the subject line with a summary,
then specify what occurred.

Step 2. Expand some of the comments to match line width expectations for comments.

Step 3. Be clearer on what a splitter is, or rather, remove the term entirely. Instead,
specify that it is the chooser for Cabal's simple build system to take an action.

Step 4. I am personally dissatisfied with one comment (mainHelper), as I don't think it's clear enough
on what one of the actions does. I was originally planning to revise the comment in a further
commit, but if I must revise, then it makes sense to make such changes immediately.

[ffaf1]

For sure, @liamzee!

[ffaf1]

Very good!

[ffaf1]

Add a merge me label and wait patiently for two days to have this merged, @liamzee.