MSVC and clang/gcc having different opinions on warnings is not as fun as i remember
=> More informations about this toot | More toots from kstatz12@discuss.systems
@kstatz12 it was never fun...
It was never anything good like "hey we found this actually undefined behavior for you"
It was always like "ah but on our platform char is {un}signed so here's two thousand places where you are missing a cast"
=> More informations about this toot | More toots from lambdageek@mastodon.social
@kstatz12 my biggest productivity boost in modern C is fucking int8_t and uint8_t
=> More informations about this toot | More toots from lambdageek@mastodon.social
@lambdageek "oh, you have a variable called x as a private field and as a throwaway variable name in a function? That's shadowing nerd" - MSVC, probably
=> More informations about this toot | More toots from kstatz12@discuss.systems
@kstatz12 @lambdageek ok but this exact problem once caused a heap corruption bug for me that wasted two days debugging so maybe I kinda wish GCC made that a warning
=> More informations about this toot | More toots from mcc@mastodon.social
@mcc @lambdageek coming from a java background I'm a follower of the one true this->x;
=> More informations about this toot | More toots from kstatz12@discuss.systems This content has been proxied by September (ba2dc).Proxy Information
text/gemini