Nov 13, 2025

I realized as I was completing the testing that I had neglected optional parameters. These can occur in an array of parameters, where positions are nulled or trailing positions are unspecified, and can happed with named parameters, where the parameter is just omitted. So you can see a couple of the types above are wrapped with an option and default value of the option type: option<double, 42>. I'll work this in tomorrow. The outcome will be that handlers can reliably bind to a fixed parameter set and the default values will simply be injected when they are allowed to be defaulted and are omitted from the call. If disallowed (not configured as optional) it's just an error for the parameter to be missing.