Open
Description
It appears to me that all CBOR parsing failures are now requiring exceptions, since #325 was merged. It appears to me that all of the current decode_cbor() implementations require exceptions or aborts. The underlying decode() and read() functions do at least have error-code-oriented variants, but in the decode_cbor() implementations, those are all turned into exceptions, AFAICT.
Without digging more deeply than my C++ expertise would easily go, I can't tell which of those are used by reflect-cpp. I also can't discern how much effort it might be for reflect-cpp to use the underlying error-code-oriented methods.
But as is, the Result and monadic features of reflect-cpp aren't really available to CBOR users.
Metadata
Metadata
Assignees
Labels
No labels