When I was playing around one of most irritating thing in Go was that I need to write a lot of type conversions, especially since there's eight "normal" integer types. In my opinion, for sake of simplicity it could be reduced.
I don't think you mean "simplicity" here. What's simpler than forcing the programmer to say what they mean? Perhaps you mean "convenience".
When I had to use Java for a project, most of the time I was casting objects around, because libA didn't use stuff libB needed etc.
Honestly, the difficulty expressed by the GP here is way oversold. I spent a decade using dynamically typed languages and I slid into Go with little difficulty. I really appreciate static typing now.
But after rethinking the issue I agree with you that's good idea, just hadn't meet place for this in my pet projects.