Swift 6

You may consider it a fanboy response but, the reality is, in some cases, xCode 7 for example, what youare asking simply may not be possible. If you're coding with Swift, iOS 7 is the lowest target possible.Once xCode 7 goes into release, xCode 6.x will only be allowed for a limited time period so, same issue.Right now, you can use xCode 6.x and as Simpsonics said, set the target all the way down to 4.3 if youwish BUT, not in Swift apps.

Plus it would help to know if you're using Xcode 6 or 7. Swift has changed in Xcode 7 and you may be using code that hasn't been updated to use it.

This is taken from the Xcode 7 beta 6 release notes:The method RangeReplaceableCollectionType.extend() was renamed to appendContentsOf(),and the splice() method was renamed to insertContentsOf(). (21972324)It seems the Swift book you use is not properly updated yet.I think the latest online version The Swift Programming Language (Swift 2) should reflect the latest changes, and if not, you can send a Bug Report.

My Xcode7 beta 6 suggested this signature:let data = try self.account.dataForKey(kPrivateKey, error: ())This may not be what you expect, but it seems both dataForKey methods are available in Swift.

A SwiftData Model cannot cross actor boundaries to avoid data races. You shouldn't make your model conform to Sendable because it still doesn't. I am currently in the same situation and as far as I can tell the best option to migrate to Swift 6 when using SwiftData is using ModelActor There are not as many tutorials and articles about it as other SwiftData topics but I believe this is the way to go. Do not return SwiftData Models from your ModelActor. This may result in data races when these models are accessed from different threads. Only return sole properties and the persistentModelIDto identify models. This is what my actor looks like: @ModelActor actor DataHandler { public func fetch(_ descriptor: FetchDescriptor) throws -> [PersistentIdentifier] { return try self.modelContext.fetchIdentifiers(descriptor) } public func update(_ persistentIdentifier: PersistentIdentifier, keypath: ReferenceWritableKeyPath, to value: T) throws { guard let model = modelContext.model(for: persistentIdentifier) as

Are you using Xcode 6.x? I can see the message you have shown only in Xcode 6.4.In that case, no way. You cannot provide C-function pointers from Swift 1.x. Use Swift 2 with Xcode 7. Or, you need to live with Objective-C codes mixed.If you got that message with Swift 2, you need to provide more info.

[quote='811117022, Capablanca, /thread/766993?answerId=811117022#811117022, /profile/Capablanca'] I haven’t grasped all the subtleties of Swift 6 [/quote] I think that’s fair to say of the entire Swift community. We’re all coming up to speed on this together. It’s also fair to say that some of the pieces are still missing. One of those things is a really good solution to the issue of progress reporting (-: However, in this case I think you’ll be OK. I see two significant challenges here: Configuration Progress reporting Lemme tackle each in turn. You need to create a configuration value in Swift Concurrency Land™ and use it in GCD Land™. If I were in your shoes I’d give your configuration value semantics. And the easiest way is to make it a struct. A typical struct is sendable because all of its components are sendable. This assumes that the configuration is fairly straightforward. If it’s complex, or very large, you may need something more complex. With regards progress, this is on

Yes it is.You can see thattestMe() func testMe() { print(Tested) }will fail.If you want some reading:w ww.speirs.org/blog/2016/6/17/thoughts-on-swift-playgrounds