fail to bridge back to MySwiftClass (rare) > My fix (#27682) should land in Swift 5.2 Bridging Swift Classes Back To Swift via Objective-C Bridging Objective-C Categories on Swift Types To Swift > Circular dependency • Generated header (MyApp-Swift.h) • Bridging header (MyApp-Bridging-Header.h) Problematic Code
Why was this setting needed? Understanding What Has Been Configured Merge Conflicts > Requires understanding Xcode’s project file format Xcode Project Size
Why was this setting needed? Understanding What Has Been Configured Slow > Modifying anything was painfully slow Merge Conflicts > Requires understanding Xcode’s project file format Xcode Project Size
in Swift sometimes too coarse grained Tooling Problems CocoaPods > Unnecessarily rebuilt after cleaning Generated Header (LINE-Swift.h) > Nearly a clean build when modified Problem Areas
Files marked dirty will propagate dirty flag to all of its extensions > OTHER_SWIFT_FLAGS = -driver-show-incremental Limiting Access to Swift Extensions Precompiling Generated Header > Mileage may vary > Usually not necessary nor recommended Quick Improvements
Done, but removed SwiftPM due to reliability issues (mostly with CI builds) (SR-10718) > Now Bazel is downloading hard-coded dependencies Current Status
Code From SwiftPM in Bazel Replace CocoaPods & Carthage With SwiftPM for Dependency Resolution > Done, but removed SwiftPM due to reliability issues (mostly with CI builds) (SR-10718) > Now Bazel is downloading hard-coded dependencies Current Status
Code From SwiftPM in Bazel Bonus: Move Code Generation to Bazel > Mostly done > No longer have to codegen unnecessarily Replace CocoaPods & Carthage With SwiftPM for Dependency Resolution > Done, but removed SwiftPM due to reliability issues (mostly with CI builds) (SR-10718) > Now Bazel is downloading hard-coded dependencies Current Status
true gains in incremental build times Build More in Bazel Improve Developer Experience > Code viewer & breakpoints working in Xcode with Tulsi > Code completion is not complete > Making modifications to code built by Bazel not great Remaining Issues
true gains in incremental build times Build More in Bazel Cache Reusability > Some differences between machines prevent build cache reuse > Mostly resolved Improve Developer Experience > Code viewer & breakpoints working in Xcode with Tulsi > Code completion is not complete > Making modifications to code built by Bazel not great Remaining Issues