The underlying types are exposed to you, like C. Go isn't adding sugar to handling numeric types: it's not autoboxing to help you with conversions, and it's no

The underlying types are exposed to you, like C. Go isn't adding sugar to handling numeric types: it's not autoboxing to help you with conversions, and it's not hiding the implementation like a scripting language. I'll admit, it's a real pain when trying to convert from one type to another (e.g., in graphics programming, where I'm changing types from internal representations to what gets drawn to the screen). For most "job" programming, it was a non-issue and I felt secure in knowing what types, sizes, and representations I'm really using.