3 ms·
I tend to agree. That said, I rather like V’s short primitive type names (i32, u32, f32, f64, etc.). But why do definitions put the type _after_ the field/var
by BonesJustice 8y ago
I tend to agree. That said, I rather like V’s short primitive type names (i32, u32, f32, f64, etc.).
But why do definitions put the type _after_ the field/variable name? So many of your type names are the same length! Think of the beautiful column alignment you could have if you put the type _first_!
- onlyrealcuzzo 8y agoI'm guessing here, but I don't think column alignment was a consideration for the ordering.
- BonesJustice 8y agoI would be concerned if it had been :).
- amedvednikov 8y agoV aligns your code automatically :) Also variables are declared with `a := value` On putting the type after the name: https://golang.org/doc/faq#declarations_backwards https://golang.org/doc/faq#declarations_backwards