ffi

Some users have specific use cases where they would benefit from being able to access the PYO3_CONFIG_FILE values in some form from the pyo3 crate.

I generally wouldn't advise this, as a lot of these config files (such as library path) are unique to the build environment so wouldn't have any useful meaning in binaries intended to be deployed on other systems.

See original comment from #2

Based on pythonnet/pythonnet#554

> #r C:\\Python\\Python35_64b\\lib\\site-packages\\Python.Runtime.DLL
> using Python.Runtime;
> dynamic np; using (Py.GIL()) { np = Py.Import("numpy");};
> using System.Collections.Generic;
> using System.Collections;
> dynamic a = np.array(new List<float> { 1, 2, 3 });
> dynamic b = np.array(new List<float> { 6, 5, 4 }, dtype:

🐛 Bug Report

Recently, related to LLVM Loader, I've seen that there's some warnings with strlen and strncpy which were not present on my version of GCC ( metacall/core#137 (comment) ). This warnings indicate that there can be an out of bounds error or similar, so it should be reviewed.

Expected Behavior

No warnings shown.

Current Behavior

Currently, a Haskell program that reports uncaught exceptions in stderr looks like this:

main :: IO ()
main = withJVM [] $ handle (showException >=> Text.hPutStrLn stderr) the_program

The call to handle is cheap enough that it should be made inside of withJVM, making the default behavior the more chatty. Thus, the same behavior could be achieved with

main :