> On Jun 16, 2016, at 9:55 AM, David Waite <[email protected]> wrote:
>
> (repost)
>
> Two comments:
>
> - I’ll specifically call out that I think treating this as an alias rather
> than a new platform is appropriate - it would be confusing for users if the
> existing #if os(osx) did not match Sierra.
>
> - Do you anticipate a separate proposal deprecating #if os(osx) ?
>
> -DW
I do not anticipate deprecating the OSX test. Swift will and can be deployed to
OS X as well as macOS. I've been tossing this around in my head for a few days
now and my thoughts are:
* the configuration test should not remain as #if os(OSX) because that's the
wrong name
* replacing OSX with macOS places an undue burden on existing code
* aliasing the two may cause issues down the road ("why does this test have two
names") but I think developers are smart enough to figure out why both
variations exist
* developers can and will still deploy to OS X for Yoze and El Cap
-- Erica
>
>> On Jun 16, 2016, at 8:29 AM, Erica Sadun via swift-evolution
>> <[email protected] <mailto:[email protected]>> wrote:
>>
>> Starting in Sierra, Apple's Mac-based OS is renamed to macOS.
>>
>> All user-facing Swift APIs must go through Swift Evolution. While this is a
>> trivial API change, I have put together a formal proposal as is normal and
>> usual for this process. Here is a draft for public comment.
>>
>> -- Erica
>>
>> Gist: https://gist.github.com/erica/f53fa6cfef9e5cf17ab139f7528edde2
>> <https://gist.github.com/erica/f53fa6cfef9e5cf17ab139f7528edde2>
>>
>> Aliasing the OS X Platform Configuration Test
_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution
