Since bumping our MSRV to 1.66 num_enum provides a catch_all variant which we can use to store yet-unknown or yet-unmapped error codes, rather than having them in a secondary enum which derives thiserror.
This also allows us to get rid of a manual match statement, which can be (but could already have been...) generated by num_enum via TryFromPrimitive before.
~Depends on #431~
Since bumping our MSRV to 1.66
num_enum
provides acatch_all
variant which we can use to store yet-unknown or yet-unmapped error codes, rather than having them in a secondaryenum
which derivesthiserror
.This also allows us to get rid of a manual
match
statement, which can be (but could already have been...) generated bynum_enum
viaTryFromPrimitive
before.