Read up a bit on this now, and it definitely looks like something I want to try out! One of the beautiful thing about C is its simplicity, and it looks like Odin has been able to keep that, while introducing some nice convenience features that I often feel like I miss when writing C.
Usually I feel like articles like this are way too sensationalist, but this Ine was actually informative and well written!
I don’t know if or when we will be sending people to mars, but knowing where there is water will in any case be crucial if we’re going to do it.
I think that’s reasonable. As long as someone is posting relevant content, there should be no obligation to interact with their own posts.
I think people talking about premature optimisation are often talking about micro-optimisations. Those are almost always unnecessary until you’ve identified choke points. Optimising the overall architecture of the code base on the other hand, is in my opinion something that should be thought about before you even start coding. That’s where the major gains can often be done anyway.
Theres plenty of cases where I would like to do some large calculation that can potentially give a NaN at many intermediate steps. I prefer to check for the NaN at the end of the calculation, rather than have a bunch of checks in every intermediate step.
How I handle the failed calculation is rarely dependent on which intermediate step gave a NaN.
This feels like people want to take away a tool that makes development in the engineering world a whole lot easier because “null bad”, or because they can’t see the use of multiplying 1e27 with 1e-30.