Before reading further, keep in mind that I just read through the INTERCAL spec and so my mind is slightly muddled. That said…
This post is giving me the feeling of “why the hell would I use go?”. Sure, the language may be simple, but this is where no generics really hurts: there is no standard library min/max implementation for integers or float32s. Why? Well, I’m only guessing here but:
math.Min/math.Max are taken by the float64 versions
The functions are trivial (but so are the float64 versions)
The stdlib designers didn’t want MinI32, MinF32, etc cluttering the namespace.
As a developer, I see a trivial but common use case needlessly complicated by the restricted featureset of the language. This does not make me want to use go in the least.
Before reading further, keep in mind that I just read through the INTERCAL spec and so my mind is slightly muddled. That said…
This post is giving me the feeling of “why the hell would I use go?”. Sure, the language may be simple, but this is where no generics really hurts: there is no standard library min/max implementation for integers or float32s. Why? Well, I’m only guessing here but:
As a developer, I see a trivial but common use case needlessly complicated by the restricted featureset of the language. This does not make me want to use go in the least.
TLDR: Casting considered harmful ?