Dan Kolsoi
After looking at #32, it seems that `build_global_string` and related `build_global_string_ptr` methods segfault when called without an active function being built on for some reason (even though the string is...
Inkwell use to have something like that, however the issue was primarily that the trait would require you to assume the global context which may not always be desired and...
We're going to want `Builder` subtypes, as an unpositioned builder can cause segfaults in many scenarios.
I'm not really sure - a JIT EE should be able to have functions added to it. Odd
Oh, yeah. I think you want `create_execution_engine` for the original JIT which allows additional functions to be added. It's older, though.
Hmm, sounds like it could be an alignment issue? Have you tried tweaking the alignment of your Rust struct?
You can use `#[repr(align(N))]`. My intuition is that your Rust and LLVM structs are aligned and/or sized differently so you're seeing garbage data from those being different.
I definitely agree that there should be shared methods across traits and possibly enums, but the tricky part is figuring out to what degree. For example, a method might be...
I think it makes sense to provide an `as_basic_value()` method for PhiValue (or some set smaller than BasicValue if applicable) which provides a BasicValueEnum for use in such a case.
The thing is that LLVM IR is very strongly typed, but the C API is far less so. With Inkwell, I want to leverage that same strongly type interface from...