Why do these two float64s have different values?

by

As per spec:

Constant expressions are always evaluated exactly; intermediate values and the constants themselves may require precision significantly larger than supported by any predeclared type in the language.

Since

912 * 0.01

is a constant expression, it is evaluated exactly. Thus, writing fmt.Println(912 * 0.01) has the same effect as writing fmt.Println(9.12). When you pin 912 to float64, the other operand of the floating-point multiplication is implicitly pinned to float64, too. Thus, the expression float64(912) * 0.01 behaves like float64(912) * float64(0.01). 0.01 is not exactly representable in a float64, thus precision is lost in a different place than in the expression float64(912 * 0.01) which arises in the argument of fmt.Println() in your first example, explaining the different results.

More Related Contents:

  1. Golang converting float64 to int error
  2. Create a generic channel
  3. Dealing with float precision in Javascript [duplicate]
  4. How to pipe several commands in Go?
  5. slice of struct != slice of interface it implements?
  6. How can I convert string to integer in golang
  7. How to dump goroutine stacktraces?
  8. Does Go compiler’s evaluation differ for constant expression and other expression
  9. Cyclic dependencies and interfaces
  10. Accessing struct fields inside a map value (without copying)
  11. Floating point equality and tolerances
  12. Why do I get a “cannot assign” error when setting value to a struct as a value in a map? [duplicate]
  13. Can I concurrently write different slice elements
  14. python floating number [duplicate]
  15. Organize local code in packages using Go modules
  16. Floating Point Limitations [duplicate]
  17. Golang defer behavior
  18. Is unnamed arguments a thing in Go?
  19. Terminating function execution if a context is cancelled
  20. Conversion of time.Duration type microseconds value to milliseconds
  21. How to delete an element from a Slice in Golang
  22. Does the Go language have function/method overloading?
  23. Go: panic: runtime error: invalid memory address or nil pointer dereference
  24. Go struct tags with underscore before function names
  25. Function declaration syntax: things in parenthesis before function name
  26. How to import local packages without gopath
  27. How can I open files relative to my GOPATH?
  28. Difference between any/interface{} as constraint vs. type of argument?
  29. Slice chunking in Go
  30. Handle maps with same key type but different value type

Leave a Comment