mainargs

Models what is known by the router about a single argument: that it has a longName, a human-readable typeString describing what the type is (just for logging and reading, not a replacement for a TypeTag) and possible a function that can compute its default value

What is known about a single endpoint for our routes. It has a name, flattenedArgSigs for each argument, and a macro-generated invoke0 that performs all the necessary argument parsing and de-serialization.

Realistically, you will probably spend most of your time calling Invoker.invoke instead, which provides a nicer API to call it that mimmicks the API of calling a Scala method.

Represents what comes out of an attempt to invoke an Main. Could succeed with a value, but could fail in many different ways.

Represents the ability to parse CLI input arguments into a type T

Has a fixed number of direct subtypes - Simple, Constant, Flag, Leftover, and Class - but each of those can be extended by an arbitrary number of user-specified instances.