go/types: use correct error position

Follow-up on https://golang.org/cl/271706 .

Change-Id: I90339987aed88b0de3ee7ebe7d413282055c260c
Reviewed-on: https://go-review.googlesource.com/c/go/+/271789
Trust: Robert Griesemer <gri@golang.org>
Run-TryBot: Robert Griesemer <gri@golang.org>
Reviewed-by: Robert Findley <rfindley@google.com>
TryBot-Result: Go Bot <gobot@golang.org>

diff --git a/src/go/types/expr.go b/src/go/types/expr.go
index 4e19f304772791f261e0f25eca2e0ef1d550f49f..eb2056125a7b71aecf3efb362cd98ec5146a09a1 100644 (file)
--- a/src/go/types/expr.go
+++ b/src/go/types/expr.go
@@ -890,7 +890,7 @@ func (check *Checker) binary(x *operand, e *ast.BinaryExpr, lhs, rhs ast.Expr, o
                        // TODO(gri) We should report exactly what went wrong. At the
                        //           moment we don't have the (go/constant) API for that.
                        //           See also TODO in go/constant/value.go.
-                       check.errorf(atPos(e.OpPos), _InvalidConstVal, "constant result is not representable")
+                       check.errorf(atPos(opPos), _InvalidConstVal, "constant result is not representable")
                        // TODO(gri) Should we mark operands with unknown values as invalid?
                }
                // Typed constants must be representable in