Re: [swift-dev] [swift] master: swift-api-digester: teach the tool to keep track of ownership attributes. (4475b07)

Just curious - what is the swift-api-digester? -Kenny > On Oct 27, 2016, at 11:55 AM, Xi Ge via swift-commits > wrote: > > Repository : github.com/apple/swift > On branch : master > Link : > github.com/apple/swift/commit/4475b0761337b3a379d0a88561a659c9c6d946db > >> -

Re: [swift-dev] [swift] master: swift-api-digester: teach the tool to keep track of ownership attributes. (4475b07)

> On Oct 31, 2016, at 12:00 PM, Kenny Leung via swift-dev > wrote: > > Just curious - what is the swift-api-digester? > swift-api-digester is a test utility to detect source-breaking API changes during the evolution of a Swift-compatible module. The tool works on two phases: (1) dumping modul

[swift-dev] swift-3.0-branch linux PR builder failure

Hi, llvm seems to be failing to build on linux PR builder for swift-3.0-branch https://ci.swift.org/job/swift-package-manager-PR-Linux/630/consoleFull#1458323263ee1a197b-acac-4b17-83cf-a53b95139a76

[swift-dev] Swift Class Encoding Standard?

Thanks all, I’ll take this info to try to come up with a draft proposal for encoding after having done deeper research into the ins and outs of the current options and decisions made. Appreciate the kind and useful responses! Tom > This is somewhat intentional. While simple names can be encode

[swift-dev] Continuation-based versus nested-function-based materializeForSet

We currently abstract over mutable property accesses using what I’ll call a continuation-based model–the materializeForSet accessor is called before an inout access, and returns a continuation callback that must be called when the inout access is completed. I think a nested-function-based model,

[swift-dev] TWISt-shout Newsletter 2016-10-31

Here is your TWISt-shout Newsletter for the week of 2016-10-24 to 2016-10-30 https://github.com/pepperdog/TWISt-shout/blob/master/2016/TWISt-shout-2016-10-31.md Enjoy! -Kenny ___ swift-dev mailing list swift-dev@swift.org https://lists.swift.org/mai

Re: [swift-dev] SE-0047 - Defaulting non-Void functions so they warn on unused results

> On Oct 30, 2016, at 5:49 AM, Jody Schofield via swift-dev > wrote: > Sorry, I'm sure this has been discussed before, but what the heck??? > > This feature is killing me. Now I have go add @discardableResult to every > function that returns a non-Void or use the ugly syntax `_ =`? > > Until