The general idea is to have something that works as follow:

CommandLineParameter<bool> MyParameter("myparameter", true, "This parameter does some very interesting thing");

// Parameter use
void doTheThing(const Config &config) {
    bool value = config.get(MyParameter);
    // ...
}

Later on the parameter can take more arguments, such as a parser for it's value, a validator to ensure the provided value is correct, a visibility parameter to know if we display it in the help or not, etc...

Once we get the basic to work, we can extend.

I like this task I can take a shot at it.

So is it assumed that the parameters are global to the state? The design becomes a little bit more efficient in some regards if the parameter as given in the example is considered global to the run of the program vs living in the "config" object.

Is it conceivable that there are multiple Config objects that point to different configurations alive in the same memory space? Or is "Config" always a part of the global state?