[swift-evolution] Nil coalescing operator precedence

Sean Heber sean at fifthace.com
Wed Jun 15 09:19:22 CDT 2016


> On Jun 15, 2016, at 7:21 AM, Vladimir.S via swift-evolution <swift-evolution at swift.org> wrote:
> 
> I believe we should not take into account any IDE features when discussing the *language*. One will write Swift script code in vim on linux, other will read in web browser on github etc.

Unrelated to anything else in this discussion, I just wanted to respond to this and say that I’m totally opposed to this line of thinking. If we continue to design languages that must accommodate the lowest common denominator in terms of tooling, we’ll never advance anything in meaningful ways. Tooling is super important and it is mostly terrible. It could be so much better. We don’t have much (any?) influence over Xcode via swift-evolution, but if the language evolves in ways where smarter, better, more advanced IDEs are the best way to use it, then Xcode will adapt and if Xcode adapts and proves a better workflow, then other tools will also adapt and everyone in any language on all platforms will eventually benefit from that exploration.

l8r
Sean



More information about the swift-evolution mailing list