Ji-Xinyou commented on issue #3244: URL: https://github.com/apache/incubator-opendal/issues/3244#issuecomment-1752298775
Now, `opendal_operator_new()` will return a `nullptr` on error. Splitting it to two functions I think will not be helpful since at least one of them will return a nullptr. Currently, we only have errorcode for opendal c binding, each error code matches an error kind such as `Unexpected`, `Unsupported`, `NotFound`, `ConfigInvalid`, etc. Is adding this will suffice or a more straight-forward error message is preferred. \cc @jiaoew1991 @Xuanwo -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
