7:52:50flip214When a type mismatch is detected during compilation (but reported "only" as a warning?!), quite a few "deleting unreachable code" notes are thrown as well.
7:53:00flip214(so the warning should be an error, I guess?)
7:53:34flip214how about dropping the unreachable notes? They get reported first and might confuse people; the important thing is the type mismatch anyway!
10:34:35aethflip214: What happens is that the code gets compiled into the runtime error that must happen. So (progn (+ "Hello" "world") 42) deletes the 42 because the previous form must be a type error since strings aren't numbers.
10:41:47aethSorry, bad example, it has to be a defun, at least in the REPL.
10:48:05aethI don't seem to get unreachable code notes.
10:55:45flip214aeth: I'm proposing to drop "unreachable code" notes that occur _after_ some bad code - they just fill up the compiler output and don't help to find the original bug.