Re: [swift-users] Swift4/iOS question

> On Aug 28, 2017, at 1:58 PM, Travis Griggs via swift-users > wrote: > > If I need to take this question elsewhere, please point me to the right list. > > I decided to take the dive this morning and give XCode9 beta and Swift 4 a > try. I’m tired of not being able to refactor. > > There are

Re: [swift-users] Can't convert to the latest version of Swift because can't find framework module

Hi, Bill. I'm afraid I don't have much to help you because this is just supposed to work, and indeed it has worked for a number of projects we've tested locally. You should be able to open the workspace, select the scheme with the application, and convert both targets at once. Is this a project

[swift-users] Swift4/iOS question

If I need to take this question elsewhere, please point me to the right list. I decided to take the dive this morning and give XCode9 beta and Swift 4 a try. I’m tired of not being able to refactor. There are two things that the importer is trying to commonly change that I’m curious about: 1)

Re: [swift-users] Using #function causes big memory leak

> On Aug 28, 2017, at 11:07 AM, Edward Connell wrote: > > I reported it 5/16 in bug reporter. Possibly that was the wrong DB? > > https://bugreport.apple.com/web/?problemID=26535526 > > No, that's correct. Thanks! -Joe __

Re: [swift-users] Using #function causes big memory leak

I reported it 5/16 in bug reporter. Possibly that was the wrong DB? https://bugreport.apple.com/web/?problemID=26535526 On Mon, Aug 28, 2017 at 8:45 AM, Joe Groff wrote: > > > On Aug 27, 2017, at 10:57 AM, Edward Connell via swift-users < > swift-users@swift.org> wrote: > > > > import Foundati

[swift-users] Can't convert to the latest version of Swift because can't find framework module

I have a small macOS application with an embedded framework, both written in Swift. Each has its own Xcode project in separate locations on my Mac, and I use an Xcode workspace to develop and build both at once. I do not use CocoaPods or Carthage. My application and framework build and run succe

Re: [swift-users] Using #function causes big memory leak

> On Aug 27, 2017, at 10:57 AM, Edward Connell via swift-users > wrote: > > import Foundation > > class A { > var counter = 0 { > //didSet { onSet("counter") } // no leak > didSet { onSet() } // huge leak > } > > var properties = ["counter" : 0] >

Re: [swift-users] Using #function causes big memory leak

> On Aug 27, 2017, at 10:57 AM, Edward Connell via swift-users > wrote: > > I reported this about a year ago, but it has never been fixed and it seems > like it should be fixed for the Swift 4.0 release. What was the SR or radar number? -Joe > > Here is a simple repro case. If you watch th

Re: [swift-users] Using #function causes big memory leak

Hi Peter, thanks for taking a look. I would expect the compiler should generate a read only static string with the name of the function whenever the #function directive is used. I would expect that should not cause a leak. If I modify the onSet function to replace a static string as the default v