go/parser - Go Issues

Go Issues Packages

go/parser

memory usage more than doubled in 1.17NeedsInvestigation

#49035 opened 1 day ago by danmillwood

4

StructType.End() can overflow the FileNeedsInvestigation

#48300 opened 1 month ago by findleyr

0

remove support for type list syntax (cleanup)NeedsFix

#48261 opened 1 month ago by findleyr

3

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

#47778 opened 2 months ago by ShoshinNikita

4

uses of function type params are not resolved in the signatureNeedsFix

#45221 opened 6 months ago by findleyr

3

composite lit fields resolve incorrectlyNeedsFix

#45160 opened 7 months ago by findleyr

1

bad error message for a badly formed func literalNeedsFix

#36750 opened 2 years ago by myitcv

4

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

#36595 opened 2 years ago by zikaeroh

3

keep parsing after error limit is reached?NeedsInvestigation

#29992 opened 2 years ago by stamblerre

12

fails to parse an invalid switch statementNeedsInvestigation

#29148 opened 2 years ago by stamblerre

2

fails when a valid function declaration follows an broken oneNeedsInvestigation

#29145 opened 2 years ago by stamblerre

1

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

#28326 opened 3 years ago by griesemer

0

redundant error message with unexpected commaNeedsFix

#24327 opened 3 years ago by dotaheor

5