Dan Kolsoi

@Michael-F-Bryan Docs are hosted [here](https://thedan64.github.io/inkwell/) though they only show the latest LLVM version since there's a flaw in rustdoc regarding documenting multiple conflicting features. https://github.com/rust-lang/rust/issues/43781 might work but it's not...

Thanks for offering to help! Feel free to pick anything from the list in the OP. The files in the `values` dir are probably the most straightforward/simplest to document.

I don't believe the LLVM C API supports any lazy JIT. Unless you mean Orc JIT - I do see `LLVMOrcCreateLazyCompileCallback`, but Orc isn't really beyond the experimental stage in...

Not much: https://github.com/TheDan64/inkwell/blob/master/src/execution_engine.rs#L526-L675

Unfortunately I do not currently have the free time to implement additional ORC support. I would certainly be willing and able to accept PRs which improve the existing implementation and...

I've only just started to support ORC. It's still very rough. We do have a wrapper on `LLVMGetFunctionAddress` already, called `get_function`. Thanks for all this great info. Hmm..

It's there, it's just hidden behind the "experimental" feature flag for the time being. There's not a ton yet, but you can find it here: https://github.com/TheDan64/inkwell/blob/master/src/execution_engine.rs#L518

I think maybe `add_global_mapping` should take a `JitFunction` as input? Or a variant of the function should.

I'm not sure. Could you explain what constitutes a global in this context? These functions are generated by the EE, but we don't have globals generated by the EE do...

Added a `get_function_address` method in ef5c3cd492dec823316e7700f183d82217b85d05