I see this as an opportunity for a smart ide dev to solve a problem. This argument/divide/preference should not exist. We're talking about tokens that are interpreted by a machine - how those tokens are display on screen in an editor should never have depended on the damn white space/tabs etc saved in the text file. They're literally meaningless and should all be standardised on file save.
We could strip all meaningless white space characters on save but we probably want to enforce a single standard to aid in unassisted reading of the code in non-code aware editors. However, If an individual has a preference for formatting style then the code editor should transparently transform their display of the code like CSS transforms HTML. Then there's no need for this colossal thread - individuals can have whatever style they want, the underlying source is the same for everyone. -- 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. For more options, visit https://groups.google.com/d/optout.
