If a language has two syntactic classes, statements and expressions, then having a choice operator in both seems somewhat redundant and bounds for confusion. If on the other hand, your language only has expressions, then there is only a single choice operator, and this whole thing doesn't matter.
Go, to me, cares about explicit and somewhat verbose notation. It cares about being small, coherent and readable more than it cares about compressing programs down to succinctness. In that vein, it often shies from syntactic sugar constructions. And I think it is worthwhile to have a language going that route. Smaller languages are way easier to learn. Language size is often a liability rather than a benefit. Other languages can try different routes. On Wed, Oct 18, 2017 at 7:19 PM Nicolas Grilly <nico...@vocationcity.com> wrote: > On Monday, October 16, 2017 at 8:37:25 PM UTC+2, Dave Cheney wrote: >> >> Prior to this recent post, this thread had been dormant for eight years. >> I think the results speak for themselves and this topic does not need to be >> revisited again. > > > At least, it proves people are searching in the mailing list archive > before posting, which is great, isn't it? ;-) > > -- > 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. > -- 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.
