You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Foo then inlines or factors out, with significant improvement in both readability and code size.
IMHO, unification with the draft behavior would be intuitive.
A check may also apply to an expression of type bool or a function call returning a list of values ending in a value of type bool. If the bool is false, check invokes the current handler with an error value of nil.
I have to admit, the translation of a false bool to a nil error is ugly. However, it would be very convenient.
The text was updated successfully, but these errors were encountered:
https://golang.org/doc/effective_go.html#maps
For instance this:
Would reduce to this:
Foo then inlines or factors out, with significant improvement in both readability and code size.
IMHO, unification with the draft behavior would be intuitive.
I have to admit, the translation of a false bool to a nil error is ugly. However, it would be very convenient.
The text was updated successfully, but these errors were encountered: