its luxury that sudden support for allman style would be backwards compatible and future proof. No airplanes would crash.
30. júl. 2017 12:35 skrifaði "Jan Mercl" <0xj...@gmail.com>: On Sun, Jul 30, 2017 at 2:06 PM <ecstatic.co...@gmail.com> wrote: > Personally I'd prefer a simple compiler option :) You must be kidding, aren't you? It would be a horrible decision to introduce such compiler option. Keywords: Python 3. The debate about semicolon injection was relevant about 7 or 8 years ago, IIRC. What's youe point actually nowadays? Do you expect to convince the community of few hundred thousands Go programmers to adjust to the few dozens complaining about the semicolon injection trade-offs and push a specification change breaking the Go 1 backward compatibility guarantee? I don't believe so. But then again, what's the goal? Honest question. -- -j -- You received this message because you are subscribed to a topic in the Google Groups "golang-nuts" group. To unsubscribe from this topic, visit https://groups.google.com/d/ topic/golang-nuts/rzLzp_Z74ik/unsubscribe. To unsubscribe from this group and all its topics, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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.
