go/parser - Go Issues

Go Issues Packages

go/parser

poor error recovery after missing function call argumentNeedsInvestigation

#58833 opened 3 months ago by adonovan

4

parser creates Stmt that causes token.File.Offset(stmt.End) to panicNeedsInvestigation

#57490 opened 5 months ago by adonovan

3

SIGSEGV in `(*resolver).resolveList`NeedsInvestigation

#52046 opened 1 year ago by bcmills

17

Decl field of type parameter identifier is nil for methods (but not for functions)NeedsFix

#50956 opened 1 year ago by aarzilli

9

StructType.End() can overflow the FileNeedsInvestigation

#48300 opened 2 years ago by findleyr

1

files parsed with mode 'parser.ImportsOnly|parser.ParseComments' can contain a comment after import declarationNeedsInvestigation

#47778 opened 2 years ago by ShoshinNikita

4

composite lit fields resolve incorrectlyAnalysisNeedsFix

#45160 opened 2 years ago by findleyr

2

bad error message for a badly formed func literalNeedsFix

#36750 opened 3 years ago by myitcv

4

inconsistent error messages when missing braces after struct/interface in return typeNeedsFix

#36595 opened 3 years ago by zikaeroh

3

keep parsing after error limit is reached?NeedsInvestigation

#29992 opened 4 years ago by stamblerre

12

fails to parse an invalid switch statementNeedsInvestigationgopls/parsing

#29148 opened 4 years ago by stamblerre

2

fails when a valid function declaration follows an broken oneNeedsInvestigation

#29145 opened 4 years ago by stamblerre

1

accept ...T as type in all parameter lists; leave it to go/types to complainNeedsFix

#28326 opened 4 years ago by griesemer

0

redundant error message with unexpected commaNeedsFix

#24327 opened 5 years ago by dotaheor

5