Closed Xitian9 closed 1 year ago
When would that be the case? (Background: I was trying to move definitions with more complexity into sub-modules.)
In the hledger
package we render some tables, and then later on need to make a line with the same width as some of the columns. If you'd prefer the complexity to be in submodules, I can change the definition of deriveColMods
instead. But I don't think unwrapping this one level of wrappers significantly increases code complexity (zipWith ($)
is not particularly simpler than zipWith4
).
I think it is fine. I am trying to keep the types opaque for the users in case they have to be changed later on.
This allows you to get that without copying over all the code manually.
Updated.
Occasionally, the ColModInfo used to generate a table is needed externally. This allows you to get that without copying over all the code manually.