Discussion in '2017.2 Beta' started by Deni35, Jul 12, 2017.
Look at this:
I'm sure the Vector3i looks much better.
I don't think it looks better but it does not look worse.
Also, saving two characters while making it more obscure to read isn't something I can get behind, so the verbose version is superior.
I wasn't even aware there was an int version. It must be unique to 2017.2.
Already use a Vector3Int as part of a voxel framework, so this new then.. maybe they should have gone with Vector3i
The .NET Framework Class Naming Guidelines includes the following point:
In this case, it seems Vector3Int is more compliant to the Naming Guidelines than Vector3i, according to the document at least.
If Vector3 were Vector3f (as it is in some other frameworks, such as LWJGL and Ogre), Vector3i would make sense. But as things are, Vector3Int is the better name IMO.
I'm not. ;-)
Verbose is always better IMHO. In today's realm of autocomplete editors, verbose naming is preferred in most cases. It requires no more typing, and is clear and unambiguous.
Don't tell me there's a Vector3Double too.
Vector3Long come back, all is forgiven.
Personally I prefer using the internal Type first, as that maps to how the rest of the syntax of C# works in my head:
IntVector3 foo = new IntVector3(0,0,0);