On Monday, 1 September 2025 at 23:47:50 UTC+1 Jason E. Aten wrote: - I don't like there being a new way to return an error, in effect hiding the fact that an error was returned inside a box. Having multiple return values with one of them being an error has become idiomatic, and I find this helps increase the understandability of code dramatically.
I agree with this but I have a slightly different view: Because the error type cannot be inside a box (because it's an interface and not a concrete type) the idiom will still require the programmer to return multiple values if an error is involved. I don't like the suggestion in the experiment that it provides alternative error handling possibilities. If we could box error types then maybe, but not otherwise. But I have to say Cliff, I really appreciate the effort you've put into this. The documentation you've written is clear and you've obviously spent a lot of time on it. I look forward to seeing how other people react and whether the experiment can turn into a proposal. -- 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 visit https://groups.google.com/d/msgid/golang-nuts/313d5d80-4929-454d-8719-a2aaa748e906n%40googlegroups.com.
