rustc should delete the source file on a type error

[pcwalton]

This feature was added to GHC; we should support it for feature parity.

See https://twitter.com/bos31337/status/116372971509121025 for more information.

Note that when a type error occurs during macro expansion, we should probably delete the file that called the macro, not the macro itself. Alternately, we could ask the user which file we should delete.

[eevee]

Interrupting the user during a compile is unacceptable. To be sure no incorrect code plagues the user's filesystem, you should delete both files.

[kingcons]

I second eevee.

[paulstansifer]

If there's an internal error in the typechecker, the compiler should delete itself.

[paulstansifer]

Oops, pressed the wrong button. I need to go throw away my computer now.

[eevee]

Nah, just your mouse.

If the compiler detects grammatically-incorrect prose in comments, should it delete the file or the user account?

[marijnh]

Following the visionary example of iOS, we should explore autocorrection. If an unresolved variable is within a certain edit distance of a known one, silently update the source code with the 'right' name.

[graydon]

Cute but I actually had to read it a couple times to recognize you were joking. Long day of dull triage. Closing.