3 ms·
Slightly off topic, but the sheer size of the ToC of the Mixing Swift and C++ page[1] makes me think I'm better off just learning and using C++. https://www.sw
by 90s_dev 1y ago
Slightly off topic, but the sheer size of the ToC of the Mixing Swift and C++ page[1] makes me think I'm better off just learning and using C++.
https://www.swift.org/documentation/cxx-interop/ https://www.swift.org/documentation/cxx-interop/
- thought_alarm 1y agoIf that kind of complexity frightens you then you probably want to stay away from C++ entirely.
- 90s_dev 1y agoWhat I mean is, if I'm going to learn complexity, I might as well go all-in on one unified language.
- duskwuff 1y agoQuite frankly, this isn't even that large. There are entire books about topics like JNI (Java <-> C) or Swig (Python <-> C); this page is fairly short given the broad scope of Swift's C++ integration.
- lillecarl 1y agoI've got no experience, but I imagine you don't have to interface with C++ too often, and when you do it's probably unlikely someone haven't written a wrapper library already. That's how the entire Python ecosystem works, either someone has made a wrapper, you make a wrapper or you use subprocess if the library has a CLI and you're not in a performance sensitive part of execution. Any language that makes programming easier is good. Modern C++ is also quite good, but I feel like there are more "nice to haves" in other languages. Reflection is one, for serializing things without boilerplate and his uncle. And just reflecting on types in general can be nice.