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

[Brandon Knope]

Where should the lack of {public} be reported then?

This seems like it falls under jira and not radar because it's in swift open source but I'm not 100 percent 

Brandon 

Sent from my iPad

> On Sep 4, 2016, at 11:48 PM, Douglas Gregor <dgregor at apple.com> wrote:
> 
> 
> 
> Sent from my iPhone
> 
>> On Sep 3, 2016, at 11:32 AM, Ben Rimmington via swift-evolution <swift-evolution at swift.org> wrote:
>> 
>> 
>>> On 3 Sep 2016, at 19:13, Brandon Knope <bknope at me.com> wrote:
>>> 
>>> Thank you! I was looking for this last night and failed. 
>>> 
>>> Why do you think {public} isn't included?
>> 
>> I don't know, but trying to reimplement __builtin_os_log_format in the overlay seems wrong. It would be better to have a variant of __builtin_os_log_format which takes a va_list.
> 
> 
> __builtin_os_log_format is implemented by Clang, not a library, and is quite involved. Implementing os_log in an overlay to provide near feature-compatibility with the C API is the right approach for Swift 3, where a more comprehensive solution (say, a general logging API based on string interpolation or similar) is way out of scope. 
> 
>   - Doug
> 
> 
>> 
>> -- Ben
>> 
>> _______________________________________________
>> 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/20160905/3c0d1830/attachment.html>