I'm in the habit of peppering my source code with #warning tags as part of my workflow. I'm sure I'm not the only one. See:
Is this something that we might see in Swift someday? Is there a philosophical objection to "false" warnings, or has this issue not been discussed?