microsoft/winmd-rs

Rust winmd parser

Rust winmd parser

A winmd parser written in Rust and based on the ECMA-335 standard. This winmd parser powers Rust/WinRT. A C++ winmd parser can be found here.

winmd-rs's Issues

Error handling is awkward with different result types

This needs to be made more idiomatic.

Make the TypeReader implicit

It would be dramatically easier to use this parser if the TypeDef and other row kinds stored a reference to the TypeReader rather than having to pass it into every method explicitly. That's the way the C++ version of winmd-rs works and its the one thing that's much easier about the library that inspired this Rust version.

Avoid boilerplate code in codes.rs

A macro should probably be used to generate the implementations of encode and decode as they are very repetitive and error prone.

Finish attribute value parsing

Populating the namespaces map is awkward

Mentioned here: #1 (review)

Avoid unsafe code in database.rs

Ideally we can avoid (most of) the unsafe code in database.rs by offsetting directly into the Database::bytes vector rather than casting to the various C-style structs for the various PE headers.

Reader::from_files should accept an iterator

Ideally we can avoid having to create a collection/array to call this function.

Mentioned here: #1 (review)

climeta & winrt-rust

I wonder if you've seen the https://github.com/Boddlnagg/climeta project, and (as the larger context), the https://github.com/contextfree/winrt-rust project?

Seems like the goal is basically the same as what you're doing here. I'm currently the maintainer of both projects, but I don't really have much time to work on it. I'm very happy that you (and Microsoft) are looking into this space officially now.
I just wonder if there's something you can reuse from the existing projects so you don't have to reinvent the wheel ;-)

Simplify match statements

I've done most of these but some remain.

Mentioned here: #1 (review)

Use map on iterator rather than minting new iterator types

From #23 (comment)

Add Azure build pipeline