Pretty sure that is what I said... duplicate the work in every case is silly, thus the goto... if no work, no need for goto
> On Sep 24, 2018, at 9:10 PM, Dan Kortschak <dan.kortsc...@adelaide.edu.au> > wrote: > > Rule: All rules are bad (including this one). > > goto is useful when there is a need to do some elaborate clean up (or > other work) at the postamble of a function, but in many cases it > becomes clearer to have the work done at the location (say in the > switch in the example in this thread). Use of judgement is worthwhile > as to whether this is true for any particular situation. > >> On Mon, 2018-09-24 at 20:11 -0500, robert engels wrote: >> You should always return from the place of return, or goto >> return_label, when a result/error needs to be formatted. >> >> See the Knuth paper I posted a while ago on using goto... > > -- > 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. > For more options, visit https://groups.google.com/d/optout. -- 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. For more options, visit https://groups.google.com/d/optout.
