-
Given an option of a sum type (`Foo` in this example):
```haskell
module Main where
import Options.Applicative
data Opts = Opts
{ flag :: Foo
, ok :: Bool
}
deriving (Sho…
-
# Context
Downstream projects such as `cardano-wallet` use `cardano-addresses` as a Haskell library.
However, this library is not published on a public repository such as Hackage or ChaP.
Such a …
-
In recent discussion I made the claim that there are situations where a package may want to state constraints on indirect dependencies. Here are a couple of examples where that applies:
1. The indi…
-
For example:
```
$ nix-build release0.nix
...
Configuring optparse-applicative-0.13.0.0...
CallStack (from HasCallStack):
die', called at libraries/Cabal/Cabal/Distribution/Simple/Configure.…
-
I want to implement `cp`-like behavior, where `many` arguments are parsed as source and then the last one as destination. But this fails with optparse-applicative. The only way which works is to swap …
-
It'd be good to have this feature
-
The package `bech32-1.1.4.1` has incorrect version bounds — it requires `optparse-applicative (>=0.18.1.0 &&
-
The migration to `pathtype` has been overall a pleasant one—it makes functions much more indicative of their purpose, and it’s caught some bugs (though not serious ones). Right now we’re an uneasy hyb…
-
A recent issue (#169) indicated to me that the current fortran-src CLI has some unexpected behaviours with respect to options and commands, that might make it tough to get started with the tool.
I th…
-
Currently there are a few different conventions in use for stack options that specify options to pass to external programs. These should be made consistent, preferably sharing an optparse-applicative…