Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Will this crate ever get a release >0.2.2? #25

Open
EndilWayfare opened this issue Jul 27, 2021 · 0 comments
Open

Will this crate ever get a release >0.2.2? #25

EndilWayfare opened this issue Jul 27, 2021 · 0 comments

Comments

@EndilWayfare
Copy link

First off, thanks for this crate. It is a lifesaver dealing with winapi!

As much as windows is poised to be a worthy successor to the "autogenerated low-level bindings to Windows APIs" problem, I'm stuck with winapi for the moment (until I can figure out how to turn a .tlb into a .winmd inside build.rs using only pure-rust or standard MSVC tools; COM bindings for a 3rd party, closed source program with unclear licensing to redistribute type library). This is my first serious foray into FFI/unsafe in Rust, with a limited amount of previous COM-in-Python (yuck) experience, and your project has been a good guide. It's instructive to see the difference between my first-order attempts at safe wrappers and the stuff in here (after I discovered it).

The latest release on crates.io is over two years old. It only has com, error, and wide modules uncommented. I'd prefer not to use git sources in my Cargo.toml, but I'll survive in the meantime :) It makes pinning a version more of a pain, as well as discovering when there are new compatible/incompatible changes and fixes. Semver spoils us.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant