Re: [swift-dev] Differences between Xcode official toolchains and tagged releases from repository

Thanks for the hint! When I built the toolchain I modified the "mixin_lightweight_assertions" preset locally to use "no-assertions" and "swift-assertions", thinking it was the appropriate combination based on a FIXME comment. I will try building it again with only "no-assertions" and report back.

[swift-dev] preprocessor and warnings for deprecated APIs...

Hello! I am working on porting my iOS app to iOS 10, using the new Notification framework. However, I still want it to work on iOS 9.*. So, I invoke both frameworks within if blocks. When I switch to iOS 10 deployment, I get a series of "deprecated" warnings on the old API. Is there a way in Swif

[swift-dev] KVO Context Param

Hey everyone, One of the things that came up in a code review today was the type of KVO's context param. If you look at the function signature it gets imported as UnsafeMutableRawPointer?. Is there ever a need to mutate this parameter, and if not can we change it to be UnsafeRawPointer? instead

Re: [swift-dev] KVO Context Param

Hi, Tyler. Swift doesn't guarantee stable addresses for anything but top-level and static variables, so you'd have to declare a 'var' to make a valid KVO context anyway. It's not a great situation, but it's unlikely to change any time soon. Jordan > On Oct 6, 2016, at 14:07, Tyler Stromberg v

Re: [swift-dev] [semantic-arc][proposal] High Level ARC Memory Operations

> On Oct 5, 2016, at 4:48 PM, Michael Gottesman wrote: >> On Oct 5, 2016, at 4:40 PM, Michael Gottesman via swift-dev >> mailto:swift-dev@swift.org>> wrote: >> >>> >>> On Oct 4, 2016, at 1:04 PM, John McCall >> > wrote: >>> On Sep 30, 2016, at 11:54 PM, Mi