I’m wondering why the resultHandler block on
RecoverableError.attemptRecovery(optionIndex, resultHandler:) is not marked
@escaping?
I’m trying to invoke some recovering code that executes asynchronously, then
reports if it was successful or not and I thought that this was the right
strategy. A
I'd like to bump this issue, since it has been some time and it hasn't been
addressed.
Thanks,
Elia Cereda
> Il giorno 03 mar 2017, alle ore 21:33, Elia Cereda ha
> scritto:
>
> I’m wondering why the resultHandler block on
> RecoverableError.attemptRecovery(optionIndex, resultHandler:) is no
>
> <https://lists.swift.org/pipermail/swift-users/Week-of-Mon-20160905/003185.html>
>
> - Dennis
>
> Sent from my iPhone
>
> On 23. Mar 2017, at 10:07 AM, Elia Cereda via swift-users
> mailto:swift-users@swift.org>> wrote:
>
>> I'd like to
Hi Kelvin,
Do you mind sharing the code you’re using? I’m looking back at some code I
wrote a while back to learn OpenGL and I see that the implementation was pretty
straightforward.
The OpenGL.GL module already provides the implementations for runtime functions
such as glEnable, glBlendFunc a
Hi,
I currently writing a demo app to teach myself the fundamentals of Metal and a
big part of that is obviously working with matrices. What I’m seeing is that
the code build them has some serious compilation time problems.
The worst case is this function, which according to -debug-time-functio
to 16),
> especially divisions which you have six of in the original.
>
> On Wed, Jun 28, 2017 at 1:51 PM, Elia Cereda via swift-users
> mailto:swift-users@swift.org>> wrote:
> Hi,
>
> I currently writing a demo app to teach myself the fundamentals of Metal and
> a bi
NSMutableArray does provide O(1) insertion and removal from the start and the
end of the array
(http://ciechanowski.me/blog/2014/03/05/exposing-nsmutablearray/).
I think the reason Swift doesn't use this design is because it stores the data
in a contiguous block of memory.
Elia Cereda
> Il
