A great down to earth talk. It's a strike contrast with usual these days "oh no they dare to call our beloved c++ as unsafe language, they simply couldn't write a proper c++ and wait for safety profiles miracles".
CPU should provide hardware support to check overflows without overhead. A function should have an optional pointer to be called in case of overflow, so if no error happens, the code doesn't waste branches and clocks checking for errors.
A great down to earth talk. It's a strike contrast with usual these days "oh no they dare to call our beloved c++ as unsafe language, they simply couldn't write a proper c++ and wait for safety profiles miracles".
Thanks for the talk
Wow! Very cool! Thanks for explaining those behaviors and those checks et al!
पहील्यांदा यु बी आणि फास्ट कोड मधला संबंध लक्षात आला.
CPU should provide hardware support to check overflows without overhead.
A function should have an optional pointer to be called in case of overflow, so if no error happens, the code doesn't waste branches and clocks checking for errors.
What do you think about using compiiler builtins for checked arithmetic?
36:03 C++ Seasoning: ruclips.net/video/qH6sSOr-yk8/видео.html