Mark Hammond

> Hi [@mhammond](https://github.com/mhammond) Do we have any plan to release free threaded version of pywin32 ? No, I've no plans to work on this and I've heard no one else...

Thanks for the contribution! Library mode is mainly needed when there are multiple UniFFI'd crates in a single library and we use the cargo metadata to help resolve some of...

> I think the first step is identifying what this is. Based on the changes, it seems like package name / crate root is all we use. Is that right?...

> My understanding is also that the only information we need from the cargo metadata is the crate root and the package name. Note that IIRC, we need this for...

> The term "library mode" is a bit unfortunate because it conflates two things: > * Use the library to find all uniffi symbols created by procmacros. That's not actually...

That's really cool! > I made an example [UniFFI+Bazel repo](https://github.com/mjpauly/uniffi-bazel-example/tree/main) to test things with, based on examples/arithmetic-procmacro If you are keen on taking this further, try adding a few different...

Hopefully obsoleted by #2175

I support the idea, but this new dependency is likely to be a problem for us - even without the new crate duplicates this introduces. I wonder if we can...

this is somewhat similar to https://github.com/jrmuizel/uniffi-rust-parse (unpolished, helped by cursor via an unrelated proejct), which is an experiment using Rust Analyzer to create metadata and avoid using a .so -...

This probably means the dependencies for pywintypes37.dll can't be found - eg, maybe the MSVC redistributables. A "dependency" tool, such as https://www.dependencywalker.com/, might be able to shed more light here.