On 14 January 2012 00:36, Andrei Alexandrescu <seewebsiteforem...@erdani.org > wrote:
> On 1/13/12 3:08 PM, Manu wrote: > >> On 13 January 2012 22:57, bearophile <bearophileh...@lycos.com >> <mailto:bearophileHUGS@lycos.**com <bearophileh...@lycos.com>>> wrote: >> >> Walter: >> >> > What's our vector, Victor? >> > >> http://www.youtube.com/watch?**v=fVq4_HhBK8Y<http://www.youtube.com/watch?v=fVq4_HhBK8Y> >> >> Thank you Walter :-) >> >> >> > If int4 is out, I'd prefer something like vint4. Something short. >> >> Current names: >> >> void16 >> double2 >> float4 >> byte16 >> ubyte16 >> short8 >> ushort8 >> int4 >> uint4 >> long2 >> >> Your suggestion: >> >> vvoid16 >> vdouble2 >> vfloat4 >> vbyte16 >> vubyte16 >> vshort8 >> vushort8 >> vint4 >> vuint4 >> vlong2 >> >> >> My suggestion: >> >> void16v >> double2v >> float4v >> byte16v >> ubyte16v >> short8v >> ushort8v >> int4v >> uint4v >> long2v >> >> Bye, >> bearophile >> >> >> I think I'd vote for leaving it as it is, swayed by the fact that the >> more ambiguous types are super-rarely used. float4/int4 has a nice >> familiarity with HLSL/Cg. >> > > All names should have a __ prepended, and then the library defines names > for them such as vec!(int, 4) that obey module lookup and all. Dumping a > wheelbarrow of confusable new keywords doesn't sound right at all. These ARE the library defined types we're talking about, defined in simd.d
