[swift-evolution] Proposal SE-0009 Reconsideration

[Charlie Monroe]

> I suspect the only issue is that there are lots of things that people would want to have as optional warnings, and it might be hard to justify why this optional warning is more important than other optional warnings all of which would benefit the user. In previous conversations, I believe "can it be linted?" has been proposed as the question to be asked for this kind of thing.

My main argument is that Swift is aspiring to be more than a language used for "apps on AppStore". As I've mentioned in the proposal, sensitive projects can't afford this class of bugs, since they are simple to make, hard to find and often you won't find them until runtime.

I know it's an extreme example, but can you imagine NASA using Swift with this kind of ambiguity without the ability to turn on such a warning? I've read several of their articles on software development and they are simply control freaks about everything. I know it's an extreme example, but the same goes IMHO with kernel development and any applications where lives are at stake.

Since Swift stresses out safety and IMHO this helps with the issue. And I don't think that it should be part of a linting tool, but as an optional safety feature of the compiler itself.

Charlie

> 
> I haven't paid attention very closely to most of these conversations and I did vote against an explicit self requirement.
> 
> -- E
>