If the (sub)step alone is comprehensible just in itself, hiding the previous (sub)steps and its context, then it is comprehensible when refactored to a separate function.
An then it is separately testable, documentable, and no collapsing esitor help is neede when viewing them main function, listing those (sub)steps. I understand that refactoring is a risk, but adding a new language feature just to keep the current unstructured code, is plain wrong. -- 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/8832e0fd-ecf2-4261-ac8e-7a0afa51ff1f%40googlegroups.com.
