OT: Leaving Rust gamedev after 3 years

Bruce Carneal bcarneal at gmail.com
Mon Apr 29 14:17:41 UTC 2024


On Monday, 29 April 2024 at 13:29:40 UTC, Monkyyy wrote:
> On Monday, 29 April 2024 at 12:04:00 UTC, Bruce Carneal wrote:
>> On Monday, 29 April 2024 at 10:15:46 UTC, evilrat wrote:
>>> On Monday, 29 April 2024 at 08:12:22 UTC, Monkyyy wrote:
>>>> [...]
>>>
>>> Yep, rule #1 for me, when see extern C/C++ type/function - 
>>> always add zero initializer for float/float arrays.
>>>
>>> Very few libraries handle nans correctly from my limited 
>>> experience.
>>
>> If you live in a world where no one checks for NaN at any 
>> point at any time and/or where a default zero will never hide 
>> an error then yep, you're gonna dislike NaN init.
>
> So, if you live in the current world you should dislike nan?

If that's the extent of your "world", yes.

>
> A little convoluted but I'll accept it your surrender

Useful discussion is more about understanding than win/lose.  My 
understanding of the pros and cons of NaN initialization has not 
changed.



More information about the Digitalmars-d mailing list