TyphoonComponentFactory.attachDefinitionPostProcessor and TyphoonComponentFactory.attachInstancePostProcessor both resolve to TyphoonComponentFactory.attach with Swift's automatic method name generation.
This causes a compilation error with Swift 3 (maybe even earlier versions; all I know is that I wasn't encountering this in Swift 1.x): myAssembly.attach(myPatcher) would fail saying that method attach is ambiguous. Unfortunately, there doesn't seem to be a workaround, so I resorted to NS_SWIFT_NAME to explicitly set the Swift method names.
TyphoonComponentFactory.attachDefinitionPostProcessor
andTyphoonComponentFactory.attachInstancePostProcessor
both resolve toTyphoonComponentFactory.attach
with Swift's automatic method name generation.This causes a compilation error with Swift 3 (maybe even earlier versions; all I know is that I wasn't encountering this in Swift 1.x):
myAssembly.attach(myPatcher)
would fail saying that methodattach
is ambiguous. Unfortunately, there doesn't seem to be a workaround, so I resorted toNS_SWIFT_NAME
to explicitly set the Swift method names.