3 ms·
http://golang.org/doc/effective_go.html#named-results http://golang.org/doc/effective_go.html#named-results It's far more convenient looking at the function de
by RamiK 13y ago
http://golang.org/doc/effective_go.html#named-results http://golang.org/doc/effective_go.html#named-results
It's far more convenient looking at the function deceleration and knowing what comes and goes instead of hunting for return statements.