On Thu, Oct 20, 2022 at 9:52 PM Daniel Lepage <dplep...@google.com> wrote: > > Sorry, I should have been clearer - what I am proposing is both try/handle > blocks and a `check` expression that triggers the handler.
Sorry, I did miss the "check". That aspect of this idea seems similar to the try proposal (https://go.dev/issue/32437). In that issue there was considerable resistance to having flow of control change as part of an expression. No other part of Go works that way: flow of control change is always a keyword, or a call to panic which can only occur in statement context. After going through the try proposal it's unlikely that we would adopt that kind of change. Ian -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAOyqgcWtQ_fEac%3Df0XJaJ_-bHEREqj3ByfirRSdZjQ7Y0Zr_7Q%40mail.gmail.com.
