> On Apr 5, 2017, at 3:13 PM, Felipe Cypriano via swift-users
> wrote:
>
> Hello,
>
> We have updated our codebase to Xcode 8.3 and to my knowledge that means we
> are now using Swift 3.1 compiler. Our first release using it - almost no
> change to code since we release very often - had a hu
Hello,
We have updated our codebase to Xcode 8.3 and to my knowledge that means
we are now using Swift 3.1 compiler. Our first release using it - almost
no change to code since we release very often - had a huge increase in
crashes related to memory all over the codebase. The solution was to
tur
> On Apr 5, 2017, at 13:32 , Jon Shier wrote:
>
> Dispatch equivalent should be dispatchMain(), unless that’s not available on
> Linux for some reason.
As seems to always be the case, as soon as I post to the list, I find that
answer. I swear I searched for 30 minutes before finding it.
I fi
Dispatch equivalent should be dispatchMain(), unless that’s not available on
Linux for some reason.
Jon
> On Apr 5, 2017, at 4:28 PM, Rick Mann via swift-users
> wrote:
>
> I've got Swift and libdispatch installed and linking under Ubuntu 16.04, but
> I'm not sure how to set up the Linux e
I've got Swift and libdispatch installed and linking under Ubuntu 16.04, but
I'm not sure how to set up the Linux equivalent of the macOS run loop in order
to service all the dispatch queues.
I'm having a hard time finding an example of how to do this. Some GCD C code
calls dispatch_main() from
On 05.04.2017 20:30, David Sweeris via swift-users wrote:
On Apr 5, 2017, at 07:49, Rien via swift-users wrote:
On 05 Apr 2017, at 16:26, Maxim Veksler via swift-users
wrote:
Hi,
Swift 3.1 compiler seems to introduces a new complier warning regarding
String(describing: )
So this line:
> On Apr 5, 2017, at 07:49, Rien via swift-users wrote:
>
>
>> On 05 Apr 2017, at 16:26, Maxim Veksler via swift-users
>> wrote:
>>
>> Hi,
>>
>> Swift 3.1 compiler seems to introduces a new complier warning regarding
>> String(describing: )
>>
>> So this line:
>> Log.info("Update name for
> On 05 Apr 2017, at 16:26, Maxim Veksler via swift-users
> wrote:
>
> Hi,
>
> Swift 3.1 compiler seems to introduces a new complier warning regarding
> String(describing: )
>
> So this line:
> Log.info("Update name for user \(fbUser)”)
Log.info(“Update name for user \(fbUser ?? “Unknown”)”
This was something that sounded like a good change but is extremely
annoying in use. Once I get time I’m going to try writing an extension on
Optional that generates a logDescription property so I don’t have to use that
awful String(describing:) API.
Jon Shier
> On Apr 5, 2017, at 1
Avoid using optionals in string interpolation or make it explicit as the
fix-it suggests.
On Wed, Apr 5, 2017 at 7:27 AM Maxim Veksler via swift-users <
swift-users@swift.org> wrote:
> Hi,
>
> Swift 3.1 compiler seems to introduces a new complier warning regarding
> String(describing: )
>
> So th
I always use `NSLog("Update name for user %@", fbUser)`. Is `Log.info` your
own implementation?
Zhaoxin
On Wed, Apr 5, 2017 at 10:26 PM, Maxim Veksler via swift-users <
swift-users@swift.org> wrote:
> Hi,
>
> Swift 3.1 compiler seems to introduces a new complier warning regarding
> String(descr
Hi,
Swift 3.1 compiler seems to introduces a new complier warning regarding
String(describing: )
So this line:
Log.info("Update name for user \(fbUser)")
Produces the warning: "note: use 'String(describing:)' to silence this
warning"
and becomes this line
Log.info("Update name for user \(St
12 matches
Mail list logo
