Irelephant@lemm.ee to Programmer Humor@programming.devEnglish · 3 days agolooks good to melemm.eeimagemessage-square46fedilinkarrow-up1736arrow-down18cross-posted to: programmerhumor@lemmy.ml
arrow-up1728arrow-down1imagelooks good to melemm.eeIrelephant@lemm.ee to Programmer Humor@programming.devEnglish · 3 days agomessage-square46fedilinkcross-posted to: programmerhumor@lemmy.ml
minus-squareskuzz@discuss.tchncs.delinkfedilinkarrow-up2·1 day agoWorks so well, and soothes the warning annoyance brain, and keeps warnings from eventually becoming errors.
minus-squarepscamodio@feddit.itlinkfedilinkarrow-up3·1 day agoIn a codebase with a lot of warnings is even better for me to add a disable comments for all the existing warning and then not allow any new one in. And then each time a part of the code needs to be touched the existing warning there should be solved too.
minus-squarejjjalljs@ttrpg.networklinkfedilinkarrow-up2·20 hours agoSeveral times I’ve set the max warnings to whatever the current warning count is, and then decreased that over time.
Works so well, and soothes the warning annoyance brain, and keeps warnings from eventually becoming errors.
In a codebase with a lot of warnings is even better for me to add a disable comments for all the existing warning and then not allow any new one in.
And then each time a part of the code needs to be touched the existing warning there should be solved too.
Several times I’ve set the max warnings to whatever the current warning count is, and then decreased that over time.