> I recently chased down a bug where something was accidentally made a class variable because a type hint was left off it by accident That's the reverse situat

> I recently chased down a bug where something was accidentally made a class variable because a type hint was left off it by accident That's the reverse situation to one I've come across - a novice accidentally wrote `a : 4` instead of `a = 4` and was surprised that `a` was still undefined. There was no error because the `4` was interpreted as a type hint.