mirror of
https://github.com/golang/go
synced 2024-11-08 19:46:23 -07:00
c65a2781be
Don't report errors if we don't have a correct type switch guard; instead ignore it and leave it to the type-checker to report the error. This leads to better error messages concentrating on the type switch guard rather than errors around (confusing) syntactic details. Also clean up some code setting up AssertExpr (they never have a nil Type field) and remove some incorrect TODOs. Fixes #24470. Change-Id: I69512f36e0417e3b5ea9c8856768e04b19d654a8 Reviewed-on: https://go-review.googlesource.com/103615 Run-TryBot: Robert Griesemer <gri@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Matthew Dempsky <mdempsky@google.com>
16 lines
397 B
Go
16 lines
397 B
Go
// errorcheck
|
|
|
|
// Copyright 2018 The Go Authors. All rights reserved.
|
|
// Use of this source code is governed by a BSD-style
|
|
// license that can be found in the LICENSE file.
|
|
|
|
// Verify that we get "use of .(type) outside type switch"
|
|
// before any other (misleading) errors. Test case from issue.
|
|
|
|
package p
|
|
|
|
func f(i interface{}) {
|
|
if x, ok := i.(type); ok { // ERROR "outside type switch"
|
|
}
|
|
}
|