From 2bd7f15dd7423b6817939b199cd2c8032e3b79cc Mon Sep 17 00:00:00 2001 From: Mateusz Poliwczak Date: Fri, 23 Jan 2026 11:15:19 +0100 Subject: [PATCH] go/scanner: document implicit semicolon in multiline comments Updates #54941 Change-Id: I62406c53b5b27742003098c77cfba0a96a6a6964 Reviewed-on: https://go-review.googlesource.com/c/go/+/738720 LUCI-TryBot-Result: Go LUCI Reviewed-by: Alan Donovan Reviewed-by: Dmitri Shuralyov --- src/go/scanner/scanner.go | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/go/scanner/scanner.go b/src/go/scanner/scanner.go index 1e68932e61..9ace335302 100644 --- a/src/go/scanner/scanner.go +++ b/src/go/scanner/scanner.go @@ -800,7 +800,9 @@ func (s *Scanner) End() token.Pos { // If the returned token is [token.SEMICOLON], the corresponding // literal string is ";" if the semicolon was present in the source, // and "\n" if the semicolon was inserted because of a newline or -// at EOF. +// at EOF. If the newline is within a /*...*/ comment, the SEMICOLON token +// is synthesized immediately after the COMMENT token; its position is that +// of the actual newline within the comment. // // If the returned token is [token.ILLEGAL], the literal string is the // offending character. -- 2.52.0