I really don't like the try proposal 
<https://github.com/golang/go/issues/32437>, because I think it hurts 
readabiity of the code.  But I think the fix is not too hard, so I made a 
counter proposal, catch:

https://github.com/golang/go/issues/32811

Catch works just like try, except it has to be a statement and has to be 
passed an error explicitly, rather than returning arguments to the left 
hand side.  This make the conversion of old code to new code look a lot 
more like normal go code.


-- 
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/37573975-8ab3-4160-ad4a-d0309825a3f1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to