3 ms·
You can't get more ambiguous to parse than {} in the context of Go. > also Julia at least is prior art Julia doesn't use curly braces for blocks and structs.
by mseepgood 5y ago
You can't get more ambiguous to parse than {} in the context of Go.
> also Julia at least is prior art
Julia doesn't use curly braces for blocks and structs.
- ethbr0 5y agoWhy not use characters from the Canadian Aboriginal Syllabics block? ᐸ & ᐳ
- mseepgood 5y agoAre we going to ask this for every Unicode character pair? They have answered all these questions in the design document: https://go.googlesource.com/proposal/+/refs/heads/master/design/43651-type-parameters.md#why-not-use https://go.googlesource.com/proposal/+/refs/heads/master/des... They thought about generics for 12 years. It's unlikely that someone who thought about it for 3 minutes on Hacker News has some epiphany that wasn't taken into consideration.
- thewakalix 5y agoIt’s a reference to a cursed Reddit post, at the top of this page.
- 0x500x79 5y agoI think this is a joke from another thread: https://www.reddit.com/r/rust/comments/5penft/parallelizing_enjarify_in_go_and_rust/dcsgk7n/ https://www.reddit.com/r/rust/comments/5penft/parallelizing_.... Also, I think it is fair to challenge the decisions here seeing as how there have been a few things chosen in Go's history that ignores prior art from other programming languages.
- deleted 5y ago[deleted]
- afiodorov 5y agomade my day