You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
go/printer: review formatting of multi-expression return statement #79515
This is a reminder issue following up on #7195 which fixed the existing formatting (CL 752220, CL 779921).
We should check that the change also works as desired if there's a mix of comp. literals and multi-line expressions in the return statement.
Hi @griesemer ! I'd be interested in investigating the remaining formatting cases in this issue, particularly the combination of composite literals and multiline expressions in a multi-expression return statement.
I noticed the issue is assigned to you, so I wanted to check first whether you'd be happy for me to investigate and potentially submit a focused regression test and fix. I can start by checking the behavior against the existing formatting changes and tests.
@dev-vmpyr Feel free to give it a shot, but please note that we may reject the solution if it doesn't seem adequate.
(As an aside, we will ignore unfiltered, obviously LLM-generated code. You need to be able to explain every line of any submission you send. Thanks.)
Activity
gabyhelp commentedon May 20, 2026
Related Issues
Related Code Changes
(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)
dev-vmpyr commentedon Oct 16, 2026
Hi @griesemer ! I'd be interested in investigating the remaining formatting cases in this issue, particularly the combination of composite literals and multiline expressions in a multi-expression return statement.
I noticed the issue is assigned to you, so I wanted to check first whether you'd be happy for me to investigate and potentially submit a focused regression test and fix. I can start by checking the behavior against the existing formatting changes and tests.
griesemer commentedon Oct 19, 2026
@dev-vmpyr Feel free to give it a shot, but please note that we may reject the solution if it doesn't seem adequate.
(As an aside, we will ignore unfiltered, obviously LLM-generated code. You need to be able to explain every line of any submission you send. Thanks.)