This feels a little better, but honestly I'm still all for angle brackets or like Watson suggested, guillamets.
*fn(T1)(fn2(T2)(fn3(T3)(v))) // 1fn[T1](fn2[T2](fn3[T3](v))) // 2fn<T1>(fn2<T2>(fn3<T3>(v))) // 3fn«T1»(fn2«T2»(fn3«T3»v))) // 4* To me, with a background in C++ and Typescript and a little bit of Rust, #3 and #4 are just natural and easier to read. Regards, Ahmed W. On Tuesday, July 14, 2020 at 9:44:53 PM UTC-5 watso...@gmail.com wrote: > Guillamets are worth consideration. They are common on European keyboards > and avoid all the syntax ambiguities. > > While a technical violation of compatibility by adding new reserved > characters, in practice I doubt this will be an issue given the semantics > of guillamets. > > Sincerely, > Watson > -- 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/f060465f-9e61-43f6-b124-22c394dc67d5n%40googlegroups.com.
