proposal: add do...for loop

[lorypelli]

Go Programming Experience

Intermediate

Other Languages Experience

JS, TS, Python, C, Java, Kotlin

Related Idea

• Has this idea, or one like it, been proposed before?
• Does this affect error handling?
• Is this about generics?
• Is this change backward compatible? Breaking the Go 1 compatibility guarantee is a large cost and requires a large benefit

Has this idea, or one like it, been proposed before?

No, it would be good to make a loop executed at least one time without duplicating code...

Does this affect error handling?

No

Is this about generics?

No

Proposal

sintax like this maybe:
i := 0
do {
i++
println(i)
} for (i < 5)

Language Spec Changes

No response

Informal Change

No response

Is this change backward compatible?

There is an entire new keyword and loop body is in a different place, I don't think so...

Orthogonality: How does this change interact or overlap with existing features?

No response

Would this change make Go easier or harder to learn, and why?

No response

Cost Description

No response

Changes to Go ToolChain

No response

Performance Costs

No response

Prototype

No response

[gabyhelp]

Related Issues and Documentation

• proposal: Go 2: Do-While Extension to For-Loops #55868 (closed)
• proposal: Go 2: fix range loopclosure bug #37061 (closed)
• proposal: Go 2: Add ability to use the slice expression [a:b] for more readable for loops and intervals. #64079 (closed)
• proposal: Go 2: run `for` loop in a goroutine with `go` keyword #36407 (closed)
• proposal: Go 2: #51613 (closed)
• proposal: Go 2: #51979 (closed)
• proposal: Go 2: #51136 (closed)
• proposal: Go 2: #53061 (closed)
• proposal: Go 2: #53072 (closed)
• proposal: Go 2: #53150 (closed)

_{(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)}

[seankhliao]

Duplicate of #55868

[lorypelli]

Duplicate of #55868

that issue was closed and I don't like using break keyword

[lorypelli]

and that would also be an infinite loop which is not that cool

[seankhliao]

Duplicate of #34896

[seankhliao]

in either case adding more syntax sugar isn't really the solution