modules will need to be built as (Objective-)C++ rather than (Objective-C)), so while we have a rough outline of how we would tackle things, it's not a solid plan. ![]() It's a large feature with some significant dependencies (e.g. ![]() (Objective-C)++ interoperability is something we absolutely want to support at some point. Are there plans for supporting Objective-C++ / C++ interop from Swift? Or would we have to shim / reimplement all of the C++ code if we wanted to adopt it? (Primarily for ComponentKit) There are also concerns about ABI stability and the binary size increase, but these will improve over time. ![]() I recently started working at Facebook, and one of our big barriers to adopting Swift internally is our substantial use of C++/Objective-C++.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |