yeah but tracing a typo like blobX:+1 v's bl0bX:+1 is no fun with some fonts!
I agree, so far I've gone with Strict which captures them but am coding function returns etc so might as well go Super.
Red, I'd find it difficult to spot blobX vs Bl0bX as well.
My favourite is typing lsit rather than list and, for some, reason, my brain fills in the gaps when I'm reading it (as we know it can from stuff like this this ).
Still, be nice to have it documented even if it's just one line of explanation