No. And GP explictly said they don't tend to make it useful, but only do it when it's easy. Making the return value of e.g. a database handle always "useful" i

No. And GP explictly said they don't tend to make it useful, but only do it when it's easy. Making the return value of e.g. a database handle always "useful" is a ridiculously dangerous idea that can lead to application bugs further down the route becaause some list/get returned an empty value to continue the pattern of "useful" empty values. The main reason there is ever a useful error next to a non-nill err is because go doesn't have a useful way to not do it.