conf

Try to parse a configuration value at the given key. Multiple confs will be tried in order.
Not on Stackage, so not searched. Parser for Haskell-based configuration files.
HTTP configuration
Read extra CLI arguments from a hledger config file.
The fixity of the constructor
Fuse a Traversal by reassociating all of the (<*>) operations to the left and fusing all of the fmap calls into one. This is particularly useful when constructing a Traversal using operations from GHC.Generics. Given a pair of Traversals foo and bar,
confusing (foo.bar) = foo.bar
However, foo and bar are each going to use the Applicative they are given. confusing exploits the Yoneda lemma to merge their separate uses of fmap into a single fmap. and it further exploits an interesting property of the right Kan lift (or Curried) to left associate all of the uses of (<*>) to make it possible to fuse together more fmaps. This is particularly effective when the choice of functor f is unknown at compile time or when the Traversal foo.bar in the above description is recursive or complex enough to prevent inlining. fusing is a version of this combinator suitable for fusing lenses.
confusing :: Traversal s t a b -> Traversal s t a b
Provides a Traversal of the types of each field of a constructor.
Conflict 409
Parse a configuration.
Confidence interval for bootstrap estimation (greater than 0, less than 1).
Over-ride this hook to get different behavior during configure.
Perform the "./setup configure" action. Returns the .setup-config file.
Try to configure all the known programs that have not yet been configured.
Try to configure a specific program and add it to the program database. If the program is already included in the collection of unconfigured programs, then we use any user-supplied location and arguments. If the program gets configured successfully, it gets added to the configured collection. Note that it is not a failure if the program cannot be configured. It's only a failure if the user supplied a location and the program could not be found at that location. The reason for it not being a failure at this stage is that we don't know up front all the programs we will need, so we try to configure them all. To verify that a program was actually successfully configured use requireProgram.
Try to configure a specific program. If the program is already included in the collection of unconfigured programs then we use any user-supplied location and arguments.
List all configured programs.
Allow depending on private sublibraries. This is used by external tools (like cabal-install) so they can add multiple-public-libraries compatibility to older ghcs by checking visibility externally.