And there is that ... LOL. I normally ignore "goto", but yes it can be turned into a looping construct. When refactoring code that uses "goto", I would try to eliminate "goto" first. If it isn't possible, then the execution flow must be so complex that it doesn't need to be broken down further.
On Sunday, January 30, 2022 at 9:24:15 PM UTC+7 Brian Candler wrote: > On Sunday, 30 January 2022 at 11:31:25 UTC Henry wrote: > >> In Go, there is only one looping construct, which is the "for" keyword. >> > > Don't forget "goto" :-) > > << ducks >> > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/108ce9eb-2378-4d78-a712-7986280cd710n%40googlegroups.com.
