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
For a function call such as fmt.Print(), the type checker infers the type (n int, err error). But for a call with an invalid argument, such as fmt.Print(undefined), the type checker infers an invalid type, even though the result type is known and is independent of the arguments. This happens for single-result function calls (like fmt.Sprint) too.
I couldn't see an obvious mistake in the go/types/call.go code.
The text was updated successfully, but these errors were encountered:
For a function call such as
fmt.Print()
, the type checker infers the type(n int, err error)
. But for a call with an invalid argument, such asfmt.Print(undefined)
, the type checker infers an invalid type, even though the result type is known and is independent of the arguments. This happens for single-result function calls (likefmt.Sprint
) too.I couldn't see an obvious mistake in the go/types/call.go code.
The text was updated successfully, but these errors were encountered: