Quoting Dave MacFarlane (2018-10-16 16:40:59) > (Also, does this mean the compiler wouldn't be able to make any > optimization assumptions regarding whether an operation is > commutative/associative/distributive?)
This is true regardless, because we aren't actually *enforcing* these properties; they're just methods. So the compiler can't rely on them any more than it can rely on implementations of io.Writer following the rules written in English in thedocs. As I mentioned in my other message, we should have a clear agreement on what these operators should mean, but the compiler won't know about it. I agree with your other points. -- 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. For more options, visit https://groups.google.com/d/optout.
