Re: Nim will silently auto convert a float64 to a float32 and loose precision... is that good? Thoughts?

[Stefan_Salewski]

The result of your code is not really surprising: As you specify the type Elem 
as an or type, you get finally two instances of vec2() proc. One produces an 
object containing float32 fields, and one producing an object containing 
float64 fields. The decision to use which of then is here taken from first proc 
argument, as the second argument is a compile time constant that one is 
silently converted.