How to handle errors in connect handlers / message handlers properly?

[SamuNatsu]

These handlers' function signature does not support any Result-like returns, so I have to wrap all the codes inside a closure and handling the ? throwed errors manually.

It seems that using unwrap or expect in these handlers will cause the entire application panic, so using a closure wrapper is the only way I found.

Is it any officially recommended way?

[Totodore]

Hey, currently there is no recommended ways.
I agree that is is quite verbose and not really user friendly.

One of the possible ways to fix this would be to allow each hander to return Result<(), E: std::error::Error> so it is possible to use the ? to abort the rest of the handler in case of error. And maybe add an on_error closure. At the moment there is nothing though.

[SamuNatsu]

Is it possible to be available in the future as a milestone?

[Totodore]

I'll write a tracking issue that summarise what I said. But I want to tackle other subjects before.

[Totodore]

#771