[swift-evolution] The great renaming and the state of new Unified Logging in Swift

[Goffredo Marocchi]

I am still not clear how os_log is supposed to be used with Swift if you are not one of the elected ones that can ride his white horse straight into iOS 10+ only land of apps ;). In Objective-C I can use a macro, as wrapper functions are banned, but in Swift? Are availability checks every time I log the answer?

Sent from my iPhone

> On 3 Sep 2016, at 17:28, Jean-Daniel Dupas via swift-evolution <swift-evolution at swift.org> wrote:
> 
> 
>>> Le 3 sept. 2016 à 06:43, Georgios Moschovitis via swift-evolution <swift-evolution at swift.org> a écrit :
>>> 
>>> Can it be corrected in Swift 4 (breaking changes etc…)?
>> 
>> Good question.
>> Maybe the core team should accept additional source-breaking changes in 3.x releases?
> 
> 
> I think the framework API mapping itself is not part of the language and is handle by Apple directly (at least for Apple specifics frameworks). I don’t know if such changes are subject to the same policy.
> 
> 
> 
> 
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160903/f5a47fa3/attachment.html>