Going from C++ through ObjC++ to ObjC to Swift is pretty onerous. There’s a lot of type reduction and conversion along the way and a lot of manual binding gener

Going from C++ through ObjC++ to ObjC to Swift is pretty onerous. There’s a lot of type reduction and conversion along the way and a lot of manual binding generation. Performance and safety footguns are plentiful through that route. If you have large existing C++ libraries, this (in theory) would really help simplify the process and reduce that mental overhead you mention. I’m not sure how your suggestion of creating wrappers is better because you’d have to still keep the C++ side for those wrappers and introduce a new intermediary layer to manage as well. Surely having one less layer is desirable?