it does not have to guess
convention dictates either one or the other
is convention enough? is it roughly the same as compiler-enforced rules? you're free to say "no" but it is not like a guarantee
Convention is just an educated guess.
>is it [convention] roughly the same as compiler-enforced rules?
No. The answer is no. I'm not only free to say "no," but if I'm honest and truthful I am compelled to say "no."
at some absolute level yes, but at any pragmatic level no, definitely not
> No. The answer is no. I'm not only free to say "no," but if I'm honest and truthful I am compelled to say "no."
nope! wrong. do not pass go, etc. -- it's a spectrum
You are simply incorrect, there's no nuance or room for interpretation. A compiler can guarantee "A or B, but not both or neither", "A or B or both, but never neither", or even "A or B or both or neither" but convention for (A, B) in Go cannot, therefore it is not as good. Go's conventions are not as good as a decent type system, there's no spectrum about it; Go is always "A or B or both or neither" with no ability to exclude impossible/nonsense cases. In Go if I want to write robust, correct code I must always handle all 2^N cases for N arguments, which no one actually does.
this is not correct
but i'm not sure how to convince you of this truth, so (shrug)
>but i'm not sure how to convince you of this truth, so (shrug)
You'd need some pretty compelling evidence to convince me that something that is not guaranteed is as good as something that is guaranteed, so I can see why you're struggling. With your admissions, all I can really say is good luck convincing me or anyone.