feat: support Result-based error handling in init methods
#754
Conversation
| #[init(ignore_state)] | ||
| #[return_result] | ||
| pub fn new() -> Result<Self, &'static str> { } |
There was a problem hiding this comment.
Yeah, so this annotation is a bit misleading when used with init because nothing is actually returned. I wonder if there is a better name for this annotation.
There was a problem hiding this comment.
Yeah, not the best name for sure. How about #[handle_result_error] or even #[handle_result]?
There was a problem hiding this comment.
Yeah, not the best name for sure. How about
#[handle_result_error]or even#[handle_result]?
I personally like the latter since it's more concise (result_error is a bit redundant), but up to you!
|
@ChaoticTempest haha, are you talking about the file tree view? I thought it was only available as a feature preview. Enabled it a few days ago and am very happy that they are finally adding something like this 😄 |
While refactoring lockable-ft example in #750 I realized that init methods could also benefit from
Result-based error handling. Also realized that I forgot to throw an error when a method that does not returnResultis marked with#[return_result].