I have the following idea [1] for decluttering error handling in go. It looks similar to others already presented, but is is different in important ways:
1) It does not interfere with or use panic 2) Is general enough that one can wrap errors with other errors or check different kinds of errors. 3) Hopefully it does not disturb the flow of code to make it difficult to read (it is similar to return, not to exceptions, it is not thrown and caught). Maybe something like this has been proposed before, but I am not aware of it. This is an informal writeup, hopefully it is understandable enough, but if not, feel free to ask any questions. Thoughts? [1] https://docs.google.com/document/d/1VUDGX_y8MPnNLBActbefFjZlp6EaaGcoflZy6OS8p9c/edit?usp=sharing -- - curiosity sKilled the cat -- 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/CACm3i_i86RozyGGAo1e8oyJw3jG4Mqv7UyziqxRr-oZ%2Bu-DqrQ%40mail.gmail.com.
