I was experimenting lately with golang's type system and encountered an interesting (or not) behaviour related to floats:
package main
import (
"fmt"
)
func main() {
doesntWork()
works()
}
func doesntWork() {
x := 1234
y := x / 100000.0
s := fmt.Sprintf("%.8f", y)
fmt.Printf("%s
", s)
}
func works() {
x := 1234
y := float64(x) / 100000.0
s := fmt.Sprintf("%.8f", y)
fmt.Printf("%s
", s)
}
I think that in the case presented in the example above, in procedure doesntWork()
, golang does not automatically "assume" float32/64
when dividing an int
by an implicit float
? Is that correct? Could anyone point me towards some docs or specs where I could learn more about how golang behaves in situations like the one above?