úÎ!;c9!      Safe4>_8Ãflags-applicativeThe possible parsing errors.flags-applicative#A flag was declared multiple times.flags-applicativeThe parser was empty.flags-applicativeThe input included the --help flag.flags-applicativeKAt least one unary flag was specified multiple times with different values.flags-applicative%A unary flag's value failed to parse.flags-applicativeA required flag was missing.flags-applicativeÓA unary flag was missing a value. This can happen either if a value-less unary flag was the last token or was followed by a value which is also a flag name (in which case you should use the single-token form: --flag=--value).flags-applicative)A flag with a reserved name was declared. flags-applicativetAt least one flag was set but unused. This can happen when optional flags are set but their branch is not selected. flags-applicativeAn unknown flag was set. flags-applicative Flags parser.There are two types of flags:Nullary flags created with  and , which do not accept a value.Unary flags created with $ and its convenience variants (e.g. , , D). These expect a value to be passed in either after an equal sign ( --foo=value$) or as the following input value ( --foo value). If the value starts with --#, only the first form is accepted.You can run a parser using  or . flags-applicativejAn human-readable explanation of what the flag does. It is displayed when the parser is invoked with the --help flag. flags-applicative The name of a flag (without the --; prefix). Names can use all valid utf-8 characters except =n (the value delimiter). In general, it's good practice for flag names to be lowercase ASCII with underscores.iThe following names are reserved and attempting to define a flag with the same name will cause an error:help, displays usage when set.swallowed_flagsm, flags in this list which are set but undeclared will be ignored rather than cause an error during parsing.swallowed_switches , similar to swallowed_flags" but for switches (nullary flags).flags-applicative}Returns a parser with the given name and description for a flag with no value, failing if the flag is not present. See also < for a variant which doesn't fail when the flag is missing.flags-applicativewReturns a parser with the given name and description for a flag with no value, returning whether the flag was present.flags-applicativenReturns a parser using the given parsing function, name, and description for a flag with an associated value.flags-applicative)Returns a parser for a single text value.flags-applicative&Returns a parser for any value with a ! instance. Prefer  for textual values since L will expect its values to be double-quoted and might not work as expected.flags-applicative=Returns a parser for a single flag with multiple text values.flags-applicativeAReturns a parser for a single flag with multiple values having a !z instance, with a configurable separator. Empty values are always ignored, so it's possible to declare an empty list as --list=# and trailing commas are supported.flags-applicativeRuns a parser on a list of tokens, returning the parsed flags alongside other non-flag arguments (i.e. which don't start with --). If the special --a token is found, all following tokens will be considered arguments even if they look like flags.flags-applicativexRuns a parser on the system's arguments, or exits with code 1 and prints the relevant error message in case of failure.   "      !"#$%&0flags-applicative-0.0.4.2-9iYFQAXBu2G1q6ZAMv5zhOFlags.Applicative FlagError DuplicateFlag EmptyParserHelpInconsistentFlagValuesInvalidFlagValue MissingFlagMissingFlagValue ReservedFlagUnexpectedFlags UnknownFlag FlagParser DescriptionNameswitchboolFlagflagtextFlagautoFlag textListFlag autoListFlag parseFlagsparseSystemFlagsOrDie$fAlternativeFlagParser$fApplicativeFlagParser $fEqArity $fEqUsage $fOrdUsage$fEqParserError$fShowParserError$fFunctorFlagParser $fEqFlagError$fShowFlagErrorbaseGHC.ReadRead