@bionicbeagle @ocornut I did take the controversial step of naming s8/u8 as s08/u08 so they would be the same number of characters...
-
-
Replying to @cmuratori
@bionicbeagle@ocornut Not sure how everyone feels about that :) u08 u16 u32 u64 s08 s16 s32 s64 r32 r64 b08 b16 b32 b645 replies 0 retweets 1 like -
Replying to @cmuratori
@cmuratori@bionicbeagle@ocornut R=real, B=bool? Don't see the problem with spelling them out. Also, uint/sint/bool/real all 4 chars :-)2 replies 0 retweets 1 like -
Replying to @tom_forsyth
@tom_forsyth@cmuratori@bionicbeagle@ocornut go shorter, name the number of bytes, not bits1 reply 0 retweets 1 like -
Replying to @bartwerf
@bartwerf@tom_forsyth@bionicbeagle@ocornut A reasonable idea, certainly... u1 u2 u4 u8 s1 s2 s4 s8 Not bad...4 replies 0 retweets 2 likes -
Replying to @cmuratori
@cmuratori@bartwerf@tom_forsyth@bionicbeagle we're entering religious debate territory1 reply 0 retweets 2 likes -
Replying to @ocornut
@ocornut@cmuratori@tom_forsyth@bionicbeagle ooh, lets talk whitespace next1 reply 0 retweets 1 like -
Replying to @bartwerf
@bartwerf@cmuratori@tom_forsyth@bionicbeagle yeah! number of spaces = number of bits in type, sounds like a win.2 replies 0 retweets 1 like -
Replying to @ocornut
@ocornut@bartwerf@tom_forsyth@bionicbeagle What about just marking where the bits go? Like u08 -> _______u s32 -> ____ssss2 replies 1 retweet 3 likes -
Replying to @cmuratori
@cmuratori@tom_forsyth@ocornut@bartwerf@bionicbeagle And f32 -> seeeeeeeemmmmmmmmmmmmmmmmmmmmmmm.1 reply 2 retweets 7 likes
@zeuxcg @tom_forsyth @ocornut @bartwerf @bionicbeagle That is the shit right there!
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.