then in try\catch

[JBBianchi]

While talking on Slack with Modood, a problematic appeared I don't think we have a solution for right now:
When trying a (set of)task(s), we can catch some errors and either retry using a retryPolicy or execute some other tasks with do. But unless I missed something, we cannot gracefully transition using then.

Shouldn't we introduce a flow directive in the catch block ?

@cdavernas @fjtirado @matthias-pichler-warrify @ricardozanini wdyt ?

[cdavernas]

IMHO it's a good bad idea: try/catch is not a switch (aka flow control).
To do what you propose, you can do something in the do, then switch. Having a then at top level plus one in the catch clause would be IMO confusing, in addition of adding a new flow control that WILL be misused (ex: throwing an error to explicitly flow using the catch clause).
The try clause is not intended, in any language I know of, to be a flow directive. It's a construct to handle an error then continue/resume the normal flow.

[JBBianchi]

My bad, I skipped the top-level then. Nevermind