Dan Kolsoi
Looks like there's actually a 181.2.0, we should update to that
I'm open to reviewing a PR with support for v19. It is not as simple as a version change. Please open a separate ticket as it is off topic here
Closing as LLVM 18 is already supported
There are some tests that are failing and need to be fixed
@jaynus are you able to fix the tests?
@jaynus bump, would like to get this into the upcoming release if possible
I don't follow; the Orc JIT is in Inkwell, so why does LLVMString need to be externally createable?
In general I've started opening up types' new methods to be public, but it's not clear to me how that would be useful for LLVMString - the type's intention is...
Changing the entire crate to be Arc based is less than ideal, as it means most types are no longer simple to copy and move around without explicit clones everywhere
Can't we move the context into the orc engine? I suppose that may not be possible with the global context