You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a trait I introduced a long time ago without knowledge of how to handle errors in rust correctly. We should remove this unidiomatic trait bound and use the enclave error instead because:
When logging the error with sgx_error_with_log, the error source is displayed as being in utils wich is not true. So important debugging information is hidden.
it is unidiomatic.
it is verbose, i.e., we need to call sgx_error()? compared to ?.
The text was updated successfully, but these errors were encountered:
This is a trait I introduced a long time ago without knowledge of how to handle errors in rust correctly. We should remove this unidiomatic trait bound and use the enclave error instead because:
sgx_error_with_log
, the error source is displayed as being inutils
wich is not true. So important debugging information is hidden.sgx_error()?
compared to?
.The text was updated successfully, but these errors were encountered: