4 ms·
Sometimes you need float packed in memory efficiently. This might be useful in graphics, for example. In general, I believe it is good to give people options.
by lmilcin 5y ago
Sometimes you need float packed in memory efficiently.
This might be useful in graphics, for example.
In general, I believe it is good to give people options. You never know what people will find useful.
But if you don't want support it and you feel it will make your language better, just don't support it.
But please, quit bitchin' about it.
Java does not support unsigned integer type and everybody is fine.
And Java devs don't write rants about how unsigned integers are useless, supporting them is annoying and everybody should just forget about them.
- rtkwe 5y agoJava 8 you have a way to treat an int as unsigned: https://docs.oracle.com/javase/tutorial/java/nutsandbolts/datatypes.html https://docs.oracle.com/javase/tutorial/java/nutsandbolts/da...
- lmilcin 5y agoOnly technically. But still, Java does not have unsigned integer types for 32 and 64 wide integers, just a way to treat them as such if you need it so much that you want to go out of your way. For example when you need to parse a binary with unsigned integers. There is no way to declare unsigned 32 or 64 bit integer.
- FreeFull 5y agoThe article didn't talk about f16 or anything like that. It just talks about some complications when implementing f16 support. I'm not sure what exactly you want the author not to bitch about.
- aseipp 5y agoThe author literally implemented fp16 support in his language. You clearly did not even read the post, which was just about the minor technical hurdles to doing so. Please learn to read next time instead of wasting everyone's time with your own useless bitching.