To be honest , I am not sure this should be a bug or a feature request
Describe the bug
I have been using WalletCore as a library in my own wallet app, and I am using it in IOS, swift and xcode, so I have been use it quite a lot recently , and find out WalletCore usually swallow all the exceptions, let me give you an example.
The follow function , it catch all exceptions , and return empty instead, there is no logging , nothing
Hi @johnnyluo, that's also right. We introduced an error system in Rust, but it's not available in C++ FFI yet.
Hope we have time this year to work on it to improve UX.
To be honest , I am not sure this should be a bug or a feature request Describe the bug I have been using WalletCore as a library in my own wallet app, and I am using it in IOS, swift and xcode, so I have been use it quite a lot recently , and find out WalletCore usually swallow all the exceptions, let me give you an example. The follow function , it catch all exceptions , and return empty instead, there is no logging , nothing
This make debug issues quite hard , at least it cost me a least more than a day to figure out why the function return empty bytes.
secp256k1Extended
If the function can bubble up the exception , or error message will greatly help debugging. I raised it here in hope we could make it better
To Reproduce
Expected behavior bubble up the exceptions
Screenshots
Additional context