The convention is that if the err == nil then the value is not nil. The exceptions to this rule are very few and usually specified in the documentation. Normally you only have to check for error.

The fact that it's a convention, and not a compiler error is the entire issue at debate here.

There is no "no value" representation for int64. The only two cases are "<int64>, nil" or "<int64>, <error>".