3 ms·
This is textbook bikeshedding. If you have a bias for C syntax, everything else will look niche, weird, or "clearly insane" to you. But there's no reason that w
by nequo 4y ago
This is textbook bikeshedding. If you have a bias for C syntax, everything else will look niche, weird, or "clearly insane" to you. But there's no reason that we should prefer C's syntactic decisions for assignment and equality operators in a non-C language. Go itself deviated from them, and the authors were instrumental to C itself.
- IshKebab 4y ago> But there's no reason that we should prefer C's syntactic decisions for assignment and equality operators in a non-C language. Yes there is - because almost every language uses the same convention, and it's a totally reasonable one. You have to have a really good reason to go against that and I don't see one. > Go itself deviated from them Go didn't deviate from the C convention. It just added an extra shorthand operator to simultaneously declare and initialise variables. The meanings of `=` and `==` are the same in Go as in C. > or "clearly insane" to you I wasn't saying the use of `=` for equality is clearly insane. `[` is clearly insane for other reasons.