Re: [swift-dev] Default deployment target for swiftc

2017-11-28 Thread Chris Lattner via swift-dev
+1 -Chris > On Nov 28, 2017, at 10:36 AM, Tony Allevato via swift-dev > wrote: > > I agree, the currently running OS seems like the right default here. > Progressive disclosure and ease of prototyping are good motivations here. If > I just want to quickly prototype

Re: [swift-dev] Default deployment target for swiftc

2017-11-28 Thread Greg Parker via swift-dev
There should not be any availability checks required in the common fast-prototyping case, where your SDK version and your running OS version are the same. Availability checks are required when some API has changed since the OS version that is your deployment target. In the fast-prototyping

Re: [swift-dev] Default deployment target for swiftc

2017-11-28 Thread Jordan Rose via swift-dev
Thanks, all. Sounds like following Clang and the interpreter is the way to go. https://github.com/apple/swift/pull/13114 Jordan > On Nov 27, 2017, at 16:44, Jordan Rose via swift-dev > wrote: > > Hi, all. Consider the following command, as run on a Mac with an

Re: [swift-dev] Default deployment target for swiftc

2017-11-28 Thread William Dillon via swift-dev
I think you'll still have to write the availability checks, because Swift will make you. I think the fixit also tells you what you need for the API you're trying to use. The confusing thing will be, though, that it'll use the fall-back path unless you explicitly set the target version. > On

Re: [swift-dev] Default deployment target for swiftc

2017-11-28 Thread Tony Allevato via swift-dev
I agree, the currently running OS seems like the right default here. Progressive disclosure and ease of prototyping are good motivations here. If I just want to quickly prototype something, I'm not going to be thinking about choosing a minimum OS; I'm just going to write something using the APIs

Re: [swift-dev] Default deployment target for swiftc

2017-11-27 Thread William Dillon via swift-dev
It would be my assumption that it would build for the currently running OS. It would be very confusing to me to have availability checks failing for an OS version lower that what I'm using. I'm sure that I would be swearing for a few hours before I finally found the obscure documentation that

[swift-dev] Default deployment target for swiftc

2017-11-27 Thread Jordan Rose via swift-dev
Hi, all. Consider the following command, as run on a Mac with an up-to-date Xcode installed: xcrun swiftc foo.swift The question: should this build for the current running OS, or the oldest macOS Swift supports (10.9)? You can always specify the deployment target OS version explicitly with