Peter Atashian
Peter Atashian
Right now the instant solution which works on stable is to transform the bindings to pass certain types by pointer and handle certain return values correctly. In the future Rust...
@vadimcn The two Rust issues are: 1. Types which are not POD are sometimes handled differently in function ABIs and need a way to mark them as such. https://github.com/rust-lang/rust/issues/38258 2....
I don't know anything about the PDB format, sorry.
Alternatively they could return `Result` and return the `Value` inside the `Err` variant.
Can we please have some focus brought to this. For many applications which combine both C and Rust and are trying to create a `cdylib`, the lack of this feature...
Currently the recommended way to export a function that you define yourself from a `cdylib` or `staticlib` is a `#[no_mangle] pub extern fn foo(...) { ... }` at the crate...
This is how I handle bitfields in winapi. Note that this likely won't work with non-windows platforms because only Windows has simple sane rules for bitfields. ``` Rust macro_rules! BITFIELD...
Bitfield support in a library buys me nothing. I need dedicated syntax in the language. Anything less than that is useless for me.
Your functions have the wrong signatures. It only manifests in a linking failure on 32bit due to the stdcall calling convention name decoration. I personally recommend getting your bindings from...
I have no idea what encoder was used. I just found it on the internet.