Is it possible to make early exit in do-try-catch block? (Like `guard`)

[anandabits (Matthew Johnson)]

@kelin

By "mixing problem" I refer this, sorry for not explaining.

Yeah, the solution for this is to require a all errors to be caught with catch and not allow unhandled errors to flow down to the else clause.

[jrose (Jordan Rose)]

@anandabits

No, I don't think it should use a different keyword. The compiler should know whether else, catch, or both are required by looking at the expressions. If try is used by any of the guarded expressions then catch is required. If unwrapping, pattern matching or boolean conditions are used then an else is required.

This would be a source-breaking change, if you're already in a context that can handle errors.

EDIT: which is not automatically to say that it can't be done, but that it should be addressed directly if you decide to propose it.

[anandabits (Matthew Johnson)]

@jrose

This would be a source-breaking change, if you're already in a context that can handle errors.

I wasn't thinking about code that is already in a context that can handle errors. It would be fine to make the catch clause optional in when thrown errors are already able to exit the scope.