All - you have the privilege of watching the sausage being made. That took
courage and much foresight from some great Apple engineers that grace these
threads.
1. File those bugs and issues in radar, but lower your expectations a bit.
That’s how I usually vent my frustrations. Just imagine t
5 PM, Gerard Iglesias via swift-users
>>>>>> wrote:
>>>>>>
>>>>>> Ok
>>>>>>
>>>>>> For the record I succeeded this transformation phase last week
>>>>>>
>>>>>> I remem
nt state. So I
>>>> filed this Apple radar against Developer Tools.
>>>>
>>>>28150447 - Swift 3 UnsafeMutablePointer conversion crashes the compiler
>>>> and IDE
>>>> Should I file a Swift bug too? Would that be helpful?
>>
y
>> supposed to use the argument $0 inside the block. Saving it and using it
>> after withMemoryRebound is probably undefined behavior. But maybe you can
>> move your ".pointee = x" into a separate function rather than using a
>> closure?
>>
>> On S
e your ".pointee = x" into a separate function rather than using a closure?
>
>> On Sat, Sep 3, 2016 at 1:12 PM, Patrice Kouame via swift-users
>> wrote:
>> Finally Success! I’m seeing my pretty little 3D twirling Metal Renderer
>> cubes again… Here’s how
>&
At least I got a Radar out of this ;-) Compilers should never burn and crash
out like this...
Regards to all, Patrice
> On Sep 3, 2016, at 1:22 PM, Patrice Kouame via swift-users
> wrote:
>
> Gerard-
>
> Excellent! Looking forward to seeing your fix (hoping you get your bo
11:39 AM, Gerard Iglesias via swift-users
>>> mailto:swift-users@swift.org>> wrote:
>>>
>>> Hello,
>>>
>>> I think that it is more secure to use stride in place of size, sometimes it
>>> is not the same value.
>>>
>>&
> Hello,
>
> I think that it is more secure to use stride in place of size, sometimes it
> is not the same value.
>
> I use it in my own use of raw bindings
>
> Regards
>
> Gérard
>
> Le 3 sept. 2016 à 10:03, Patrice Kouame via swift-users
> mailto:
gt; I just updated a small Metal project of mine to Swift 3. I ran into some
> compiler (playground) crashes, but it does seem to work most of the time.
> Although I only have 1 buffer :-)
> https://github.com/jtbandes/Metalbrot.playground
> <https://github.com/jtbandes/Metalbrot.
Hi all -
I’m converting Apple’s Swift Sample "Adopting Metal II: Designing and
Implementing a Real-World Metal Renderer” in Xcode 8 beta6 to the latest
UnsafeMutablePointer API for untyped memory access.
Changes are necessary in MetalView.swift (Apple hasn’t updated their sample
code for the
he App Store with any alternative tool chain
> (such as Swift 3).
> On Fri, Jun 17, 2016 at 10:59 Patrice Kouame via swift-users
> mailto:swift-users@swift.org>> wrote:
> Hi Jordan - thanks for the quick reply (especially in the middle of WWDC!)
>
> I suspected as much w
El
> Capitan; if you haven’t already, please file a bug report at
> bugreport.apple.com <http://bugreport.apple.com/>!
>
> Best,
> Jordan
>
>> On Jun 16, 2016, at 17:31, Patrice Kouame via swift-users
>> mailto:swift-users@swift.org>> wrote:
>>
>
Swift 3.0 for Mac is currently being distributed with Xcode 8 beta.
Will a swift 3.0 toolchain for Xcode 7.3.x ever happen?
Currently having issues with the beta on El Capitan and my machine
is (apparently) no longer a candidate for future MacOs versions, notably Sierra.
Thanks in advance.
_
13 matches
Mail list logo
