> On Jun 19, 2016, at 6:35 PM, Maury Markowitz via swift-users
> wrote:
>
> All true, except, of course, when one is working with strings that really do
> work perfectly weel qwith 1...2, like the strings I'm processing, which came
> from 80-column punch cards originally used with LLNL's CDC
> On Jun 17, 2016, at 10:38 PM, Brent Royal-Gordon
> wrote:
> The standard library includes definitions of these subscripts
But how would one select those in the Xcode UI? The documentation doesn't link
off the error (AFAIK) itself, only the code. So one could select, say, the var
the error is
It probably will. In WWDC videos, it was said you can use both Swift 2.3
and 3.0 in Xcode 8. Xcode 8 will be released together with iOS 10 and macOS
10.12. Swift 2.3 is provided to those who don't want to move to Swift 3.0
rapidly.
Zhaoxin
On Mon, Jun 20, 2016 at 4:22 AM, Brent Royal-Gordon via s
> I'm migrating one of my project to Swift 3 (xcode 8 beat release).
> Most of the changes were pretty strait-forward, but I have one required
> change that is still blocking me :
> In my code, I retrieve the current dispatch queue name using that code :
>
> let queueName = dispatch_queue_get_la
> I'm migrating one of my project to Swift 3 (xcode 8 beat release).
> Most of the changes were pretty strait-forward, but I have one required
> change that is still blocking me :
> In my code, I retrieve the current dispatch queue name using that code :
>
> let queueName = dispatch_queue_get_la
> We would like to migrate our iOS apps to Swift 3 and iOS 10. However, we also
> want to be able to submit iOS 10 apps when iOS 10 is released.
>
> Does anyone know if Swift 3 will be released alongside iOS 10? Can we submit
> Swift 3 apps to the App Store when iOS 10 goes GM?
It seems unlikel
I’ve got an answer on Twitter for that behavior:
https://twitter.com/phausler/status/743927492096851969
I’ve anyone like me needs Data to have a specific capacity and still be
non-optional, here is how I build a workaround (Data and Data.Deallocator
aren’t fully implemented yet, thats why I’m u
Not quite:
Swift’s policy on memory allocation failure is that fixed-size object
allocation is considered to be a runtime failure if it cannot be handled.
OTOH, APIs that can take a variable and arbitrarily large amount to
allocate should be failable. NSData falls into the later category.
Source
As I understand it, that’s not an error in the ‘try’ sense of the word. If that
failure happens, it’s a catastrophic issue which should bring down the
application.
So the initialiser shouldn’t be failable; you’re right. File a bug at
bugs.swift.org.
Karl
> On 18 Jun 2016, at 06:06, Saagar Jha
Hi all,
I'm migrating one of my project to Swift 3 (xcode 8 beat release).
Most of the changes were pretty strait-forward, but I have one required change
that is still blocking me :
In my code, I retrieve the current dispatch queue name using that code :
let queueName = dispatch_queue_get_label
Hi all,
We would like to migrate our iOS apps to Swift 3 and iOS 10. However, we also
want to be able to submit iOS 10 apps when iOS 10 is released.
Does anyone know if Swift 3 will be released alongside iOS 10? Can we submit
Swift 3 apps to the App Store when iOS 10 goes GM?
—Florian
11 matches
Mail list logo
