Is it already a known issue that a «for [true] { ... }» loop whose only
exit path is through return statements inside the loop (i.e. no break
statement) will produce the compiler error "missing return at end of
function" if you don't put a meaningless "return ..." statement after
the loop?If this issue is not already known, will someone who has a github account please file this issue for me? Thanks...Marvin -- 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/20190610004002.ltcv36765lkn75xp%40basil.wdw. For more options, visit https://groups.google.com/d/optout.
