sheaf

> @gbaz It should be a blocker but the checkbox > > > Ensure all documentation is up-to-date relative to the exposed API. > > is ticked; so I assume...

I have updated the user's guide and addressed the review. Note that the user's guide contains links to pages that don't exist yet, e.g. [this Hackage page ](https://hackage.haskell.org/package/Cabal-hooks/docs/Distribution-Simple-SetupHooks.html) which will...

I've been applying a few fixes, in particular to the `Binary` instances of datatypes involved in pre-build rule. The main point is that we want to be able to treat...

> Sub component targets had never been implemented and that is mostly dead-code. I think we should consider removing this feature, including from cabal-install. I had PR that did that...

I think this refactor still makes sense, but nothing important depends on it right now.

> @sheaf: The Gods have not heard your prayer, it seems. Is `generic-lens-1` still relevant for you today? Maybe you have a fork? Yes, it is relevant to me because...

> I think we would need to create a release branch in order to do this nicely. Is this still important to you @sheaf ? Yes, I am still using...

If you can provide a branch I would be happy to rebase the changes in this PR, perhaps with some additional changes to squash the current warnings. I'm not sure...

I agree that we need something that emulates the functionality of named parameters, but I find this approach to be rather syntactically heavy. How are optional fields handled? For instance...

But you'd want a type error if the user doesn't pass in one of the required arguments, no? I don't think that there are sensible default records in general, there...