A shared utility crate to locate python would help us in build.rs as well as other crates in the ecosystem. As first suggested on Gitter:

@gilescope:matrix.org Also I wonder if we could create a where’s wally crate but for python. There seems to be quite a few rust applications trying to find python. I think it would be great to centralise that problem in a single crate - E.g.: https://gith

I implemented Decoder on a type that crashes the VM with a SIGBUS.

I made a minimal reproducible example in this repo: https://github.com/elbow-jason/why_sig_bus

Environment

N/A

Details

This code:

Environment.SetEnvironmentVariable("PYTHONPATH", $"{pathToVirtualEnv}\\Lib\\site-packages;{pythonPath}\\Lib", EnvironmentVariableTarget.Process);

from the wiki references a variable pythonPath that isn't defined. Is that supposed to be `pathToV

when option dump-preprocessed-input is used, BINDGEN_EXTRA_CLANG_ARGS is evaluated AFTER handling dump-preprocessed-input which result errors like "head files not found" etc in cross-compiling.

I'm trying to convert the C code for TaskScheduler COM to rust, and currently stuck with the VARIANT argument of ITaskService::Connect:

    //  Create an instance of the Task Service.
    let mut p_service: *mut ITaskService = unsafe { std::mem::zeroed() };

    let hr = unsafe {
      CoCreateInstance(
        &TaskScheduler::uuidof(),
        ptr::null_mut(),
        CLSCTX_IN

was just watching the C++ Now presentation on Julia and C++ (https://www.youtube.com/watch?v=hvnxY3NjHQ4) and noticed in the section on Cxx.jl (around 48 minutes in) that there is a special assignment syntax in the REPL ":=" for assigning C++ results back to a Julia variable.

I don't see this documented anywhere here in the docs.

Our ruby dependencies are very old and were never updated and yajl-ruby contains security vulnerability.
it would be nice to update those and make some instruction how to update them in the future.

This issue clarifies the usage of this library with other projects and describes terms of usage.

• This library, provided under RPL license can be used for free for any open-source projects without any limitations while source code of these projects or libraries is also open-sourced.
• For open-source libraries that are distributed under more permissive license types like MIT a

Right now, it is expected that rustc be on PATH. That shouldn't be the case.

Also, we ought to be able to pass in more rustc options.

It's mostly about generating a useful type name, for error reporting. Using typename crate is one option.

The instructions in the README for running the example suggest that this command:

ghc MySampleGen.hs

can successfully build MySampleGen.hs, but this is false since MySampleGen.hs has import statements.
A quick look at build.sh reveals that ghc should actually be run with the -package-db flag. However, the script references a directory outside of the repository and there is no docu