OT: Leaving Rust gamedev after 3 years

[Monkyyy]

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:
>>> On Monday, 29 April 2024 at 03:51:09 UTC, Bruce Carneal wrote:
>>>> [...]
>>>
>>> Because you get to debug a silent runtime error all the time, 
>>> and at this point I just assume it's a float being nan
>>>
>>> I'm pretty sure this is just the gpus reaction to nan, draw 
>>> calls being ignored
>>
>> 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?

A little convoluted but I'll accept it your surrender