2 ms·
true, good point. And having the power to ignore the convention is good, too.
by marcus_holmes 6y ago
true, good point. And having the power to ignore the convention is good, too.
- masklinn 6y ago> And having the power to ignore the convention is good, too. Mistakenly not handling errors is not "the power to ignore the convention", it's "the language is half assed". "The power to ignore conventions" is being allowed but having to explicitly ignore the error, aka that the second and third cases trigger errors, and that you'd have to write: y, _ := fmt.Println("Bar") println(y) _, _ = fmt.Println("Qux") (also note how you can not use `:=` in the second case, because that requires that there be at least one new variable on the LHS)
- marcus_holmes 6y agoThe language allows you to ignore the convention. There is a plethora of tools available to allow you to detect if you did that when you didn't mean to. It's just that the compiler doesn't enforce it.
- pjmlp 6y agoGiven that Go also supports binary packages, those tools won't help much there.