this sort of thing came up for me recently, in that i was thinking nicer built-in's would operate like this;
float32 * float32 = float64 so also uint - uint = int in a way, type safety (native type isolation) is kind of causing an issue, and that maybe always using big (long) numbers during development, so you have to mathematically correct answer, then optimise to native types, would be better. but that would only be 'nice' if big were a built-in. -- 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.
