> all types are annotated all the time (to be shown or hidden via editor flag, or on hover), and the annotations are updated in response to actions taken within

> all types are annotated all the time (to be shown or hidden via editor flag, or on hover), and the annotations are updated in response to actions taken within the editor So there are two possible reasons I can see for automatically "annotating" all the types: - Caching that info to easily show in the editor (which is a good feature, but many editors already do this without having to modify the source; it happens entirely editor-side) - Using the "current" inferred type as a jumping-off point for determining the "next" inferred type The second was my original interpretation, and what sounded so distressing as a user Consider this situation: 1. Your program and the inferred types are in one state 2. You modify some code which changes an inferred type 3. You change the (visible) code back to what it was previously, but now the inferred type is different because it was partially based on the previous inferred type This is what sounds like a nightmare, assuming I understand correctly that it's possible on the described system. The inferred types are now a state machine, where it matters not just what code is on screen, but how it got there.