File: noparse.go.in

package info (click to toggle)
golang-golang-x-tools 1%3A0.5.0%2Bds-1
  • links: PTS, VCS
  • area: main
  • in suites: bookworm, bookworm-backports
  • size: 16,592 kB
  • sloc: javascript: 2,011; asm: 1,635; sh: 192; yacc: 155; makefile: 52; ansic: 8
file content (24 lines) | stat: -rw-r--r-- 838 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
package noparse

// The type error was chosen carefully to exercise a type-error analyzer.
// We use the 'nonewvars' analyzer because the other candidates are tricky:
//
// - The 'unusedvariable' analyzer is disabled by default, so it is not
//   consistently enabled across Test{LSP,CommandLine} tests, which
//   both process this file.
// - The 'undeclaredname' analyzer depends on the text of the go/types
//   "undeclared name" error, which changed in go1.20.
// - The 'noresultvalues' analyzer produces a diagnostic containing newlines,
//   which breaks the parser used by TestCommandLine.
//
// This comment is all that remains of my afternoon.

func bye(x int) {
	x := 123 //@diag(":=", "nonewvars", "no new variables", "warning")
}

func stuff() {
	
}

func .() {} //@diag(".", "syntax", "expected 'IDENT', found '.'", "error")