Seems like an interesting effort. A developer is building an alternative Java-based backend to Lemmy’s Rust-based one, with the goal of building in a handful of different features. The dev is looking at using this compatibility to migrate their instance over to the new platform, while allowing the community to use their apps of choice.
That’s a kinda terrible way to do it compared to letting it bubble up to the global error handler.
You can also use optional in java if you want a similar pattern but that only makes sense for stuff where it’s not guaranteed that you get back the data you want such as db or web fetch
You can bubble up the Error with
?operator. It just has to be explicit (function that wants to use?must return Result) so that the code up the stack is aware that it will receive Result which might be Err. The function also has defined Error type, so you know exactly which errors you might receive. (So you’re not surprised by unexpected exception type from somewhere deep in the call stack. Not sure about Java, but in Python that is quite a pain)Edit: To provide an example for the mentioned db fetch. Typically your query function would return
Result(Option). (SoErrif there was error,Ok(None)if there was no error, but query returned no results andOk(Some(results))if there were results) This is pretty nice to work with, because you can distinguish between “error” and “no resurts” if you want, but you can also decide to handle these same way with:query() .unwrap_or(None) .iter().map(|item| do_thing(item))So I have the option to handle the error if it’s something I can handle and then the error handling isn’t standing in my way. There are no try-catch blocks, I just declare what to (not) do with the error. Or I can decide it’s better handled up the stack:
query()? .iter().map(|item| do_thing(item))This would be similar to exception bubbling up, but my function has to explicitly return Result and you can see in the code where the “exception” is bubbled up rather than bubbling up due to absence of any handler. In terms predictability I personally find this more predictable.
But like, what kind of error are you gonna handle that’s coming from the DB, if it’s something like a connection error because the DB is down, then you are removed out of luck you can’t handle that anyway, and you probably shouldn’t, not from the layer you are calling your DB from, that’s a higher level logic, so bubbling Errors there make sense.
and if it’s an “error” like findById doesn’t always return something, that’s what the Optional pattern is for.
what you have described to me seems like a worse version of the checked/unchecked exception system.
I could return 500 (getting
Error) instead of 404 (gettingNone) or 200 (gettingSome(results)) from my web app.Or DB just timed out. The code that did the query is very likely the only code that can reasonably decide to retry for example.