spikespaz[m]: > <@spikespaz:envs.net> Under no circumstance should there be a function that takes an arbitrary `Command`. There is always a function that dispatches the command and wraps it with behavior. There is a contract that each of these commands is used in a particular manner, none of them are to be treated in the same manner.
> 
> The `pmbus` crate defines functions which use these command codes according to spec, and then a manufacturer crate can provide an extension trait that *adds* command functions. But generally, a `Command` enum is not useful.

My device-driver project doesn't do that