That probably wasn't as clear as it could have been. I believe what he was actually referring to is that constants disappear after compile and that there's no runtime access to them e.g. there's no "reflect.Constant" or the like and that he therefore had to create a variable even though the value is always zero.
Excellent talk! Thank you.
22:37 "There's no constants in Go", what?
That probably wasn't as clear as it could have been. I believe what he was actually referring to is that constants disappear after compile and that there's no runtime access to them e.g. there's no "reflect.Constant" or the like and that he therefore had to create a variable even though the value is always zero.