Swift 3 Naming Collision

[felix-dumit]

When the objc 'continueWith' methods for BFTask get imported into swift 3, they end up colliding with the continue keyword.

Since this objc method:

- (BFTask *)continueWithBlock:(BFContinuationBlock)block;

becomes:

func continue(with block:BFContinuationBlock)

Possible solution would be:

- (BFTask *)continueWithBlock:(BFContinuationBlock)block NS_SWIFT_NAME(continueWith(block:));

Update:
If you call the continue with the named parameter the compiler understands it. So this issue really only applies if trying to use trailing closures.

[nlutsenko]

This sounds like a good potential improvement for method names.
Please consider using Bolts-Swift for pure Swift projects :P

[jyoon17]

How do I use Parse iOS SDK with Bolts-Swift?

[Vortec4800]

I am also running into this. While I would prefer to use Bolts-Swift, the Parse SDK calls for Bolts-ObjC so that's what I get.

[ziadtamim]

Same issue here.

[gesabo]

Same here

[singhnitesh]

Hi,
When I try to use the continueWithBlock method in swift3, I get a segmentation fault error.
I am using a chat library/framework which is in objc and uses bolts (v1.8.4), whenever I try to call continue(successBlock: or continue methods on a task, I get this error. Any advice?