daniellansun opened a new pull request, #3247: URL: https://github.com/apache/groovy/pull/3247
## Summary GROOVY-12641 (GEP-19) accepts `case Type name ->` as a type pattern. Two `ParserNegativeSyntaxTest` fixtures that used that form as their later syntax error therefore began to parse, so `expectParseError` failed with "expected parse to fail" — the only reds on Build-and-test across the CI matrix. Those scripts exist to prove that a paren group the parser has already closed is not reported as a missing `)`. The type-pattern `case` labels stay; each script now ends in `def y = 1 +`, the same dangling operator already used by the method-parameter and parenthesised-call cases. That is still a recognition failure, so a closed record header or `for` header ahead of it must not move the caret. ## Change - Single file: `ParserNegativeSyntaxTest.groovy` - Keep type-pattern cases; point the deliberate trailing error at `def y = 1 +` ## Related - https://issues.apache.org/jira/browse/GROOVY-12694 - https://issues.apache.org/jira/browse/GROOVY-12641 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
