> For me personally, debugging is difficult enough without needing to worry that the compiler is going to maintain state across multiple runs. Ooh, the idea ma

> For me personally, debugging is difficult enough without needing to worry that the compiler is going to maintain state across multiple runs. Ooh, the idea makes me shudder. I remember looking at a project's makefile which called a custom build script where the README said to run the buildscript twice-- once to generate some state, and a second time to compile stuff using that state. Without any comments provided, the makefile called the custom buildscript three times in a row. I can't even imagine the superstition and cargo culting that would arise from an IDE "helping out" by analyzing who has changed what, when, and in what order they changed it. Please paste a new empty function named "momo" here before doing a release. Also make sure your blinds are closed before compiling.