Re:Tom Duff: Reading Code From Top to Bottom (1999)
by enneff on Sunday June 05, 2011 @04:34AM
(#2621643)
Go's defer feature, combined with named return values, lets you do this:
func someFunction(b bool) (i int) {
defer func() {
log.Printf("I'm returning %d", i)
}()
if b {
return 1
}
return 0
}
For more on defer, see this blog post: http://blog.golang.org/2010/08/defer-panic-and-recover.html
Re:Tom Duff: Reading Code From Top to Bottom (1999)
by cpeterso on Sunday June 05, 2011 @01:21AM
(#2621374)
The single return is also useful for post-condition assertions of return values and internal state.
Re:Tom Duff: Reading Code From Top to Bottom (1999)
by jtolle on Sunday June 05, 2011 @01:52PM
(#2622466)
This of course exemplifies why it's impossible to declare almost any technique categorically "good" or "bad". Sometimes early returns make code shorter and more clear. Sometimes the opposite. To borrow from Stroustrup, experience and taste matter a lot.
Re:Tom Duff: Reading Code From Top to Bottom (1999)
by alisey on Sunday June 05, 2011 @12:27AM
(#2621299)
In dynamic languages you can do this:
some_function = function() {
if (...) return 1;
if (...) return 2;
}.log("It's important I log that I'm returning");
Re:Tom Duff: Reading Code From Top to Bottom (1999)
by palish on Saturday June 04, 2011 @11:44PM
(#2621231)
int some_function( some_variable ) {
log("Its important I log that I'm returning %d\n", (some_variable ? 1 : 2));
return (some_variable ? 1 : 2);
}
int some_function( some_variable ) {
}If its not obvious why this is superior...