Jason Novinger@programming.devM to Python@programming.dev · 16 days agoPython Performance: Why 'if not list' is 2x Faster Than Using len()blog.codingconfessions.comexternal-linkmessage-square53fedilinkarrow-up166arrow-down14cross-posted to: technology@lemmy.world
arrow-up162arrow-down1external-linkPython Performance: Why 'if not list' is 2x Faster Than Using len()blog.codingconfessions.comJason Novinger@programming.devM to Python@programming.dev · 16 days agomessage-square53fedilinkcross-posted to: technology@lemmy.world
minus-square🇦🇺𝕄𝕦𝕟𝕥𝕖𝕕𝕔𝕣𝕠𝕔𝕕𝕚𝕝𝕖@lemm.eelinkfedilinkEnglisharrow-up1·14 days agoUr function args if fucked up should always throw an error that’s the entire point of python type hints
minus-squarelogging_strict@programming.devlinkfedilinkarrow-up1·11 days agotype hints are static, not necessarily runtime. A chaos monkey throws everything at everything to see what breaks. That won’t be caught by perfect type hints, which is merely one tool in the toolbox. and when things break, often hear WAD, works as designed. Or some other nonsense excuse.
Ur function args if fucked up should always throw an error that’s the entire point of python type hints
type hints are static, not necessarily runtime.
A chaos monkey throws everything at everything to see what breaks.
That won’t be caught by perfect type hints, which is merely one tool in the toolbox.
and when things break, often hear WAD, works as designed. Or some other nonsense excuse.