4 ms·

Neither do I. Compiling to LLVM IR will enable Apple's tooling to generate correct binaries for the platform (actually nowadays Apple will do it for you through

Neither do I. Compiling to LLVM IR will enable Apple's tooling to generate correct binaries for the platform (actually nowadays Apple will do it for you through the use of LLVM bitcode for App Store submissions). There's still an issue of using the correct iOS APIs for the job, but that issue is certainly also there when compiling to C code. Neither do I agree with the statements about C code being "easier to use"; it is still generated code and it will most likely not be the nicest code to work with.

invalidname 11y ago
You can open it in a debugger. C is something pretty much every developer knows and has a ton of documentation. LLVM is nicely documented but not exactly in that league. Its more like working with Java bytecode, possible not trivial. E.g. if you have a bug in the LLVM translation code, good luck tracking that... With ParparVM just open it in the debugger and see what went wrong. Look at the referenced quote in the readme from a guy actually going thru the LLVM path (CEO of RoboVM). Its theoretically easy but in all practicality its pretty far from easy and you have no way of knowing what Apple will do with LLVM in the future. But they pretty much guaranteed they will support C as its an officially supported language.