go/printer - Go Issues

Go Issues Packages

go/printer

deletes or inserts AST types into codeNeedsInvestigation

#33479 opened 4 months ago by stamblerre

2

panic on large Go file of length >= 1<<30NeedsInvestigation

#30121 opened 10 months ago by tsenart

9

consider using last position for nodes with no positionNeedsInvestigation

#28988 opened 1 year ago by griesemer

1

line directives specifying columns must stay in place relative to next tokenNeedsFix

#24326 opened 2 years ago by griesemer

1

blank lines at top/bottom of composite literal handled differently by gofmtNeedsDecision

#23143 opened 2 years ago by willfaught

3

adjust formatting of structs with unexported fieldsNeedsFix

#18264 opened 3 years ago by dsnet

20

confusing indentation for nested structs

#16371 opened 3 years ago by tbertelsen

17

consider permitting one-line "enum" const declsNeedsDecision

#13403 opened 4 years ago by griesemer

5

unexpected handling of indented comment

#12822 opened 4 years ago by griesemer

1

"Line of stars" detection false positive for commented out block of code with each line dereferencing a pointer.

#12164 opened 4 years ago by dmitshur

2

AST rewriting and then formatting results in mangled godocs

#11775 opened 4 years ago by mdempsky

3

force multiline literal to end with } on line by itself

#10570 opened 4 years ago by nightlyone

14

wonky alignment when mixing embedded and typed fields along with struct tags in a struct definition

#7199 opened 5 years ago by gopherbot

2

match indentation when returning multiple composite literalsSuggested

#7195 opened 5 years ago by dsymonds

7

printed output cannot be parsed if comments are retainedThinking

#6554 opened 6 years ago by adonovan

4

think about format for chained callsThinking

#5351 opened 6 years ago by gopherbot

5

unhappy formatting of const declaration

#4808 opened 6 years ago by griesemer

6