firecracker-microvm/versionize_derive

Exports the Versionize derive proc macro that generates the Versionize implementation for structs, enums and unions by using structure annotations.

versionize_derive's Issues

enums: add support for versioned deserialization

Crates.io documentation.

Currently the crate is publish with almost no docs.

Refactor array deserializer code for structs and unions

The generate_array_deserializer methods for StructField and UnionField are very similar and should be refactored to deduplicate the logic.

cargo update breaks versionize_derive compilation.

I have a project which has versionize_derive v0.1.4 as a dependency. According to my Cargo.lock, this crate currently depends on syn v1.0.109. Since the release of syn v2.0.0 a few days ago, cargo update updates syn to v2.0.4, which breaks the build of versionize_derive.

In the 0.1.4 release of versionize_derive, Cargo.toml contains this line:

syn = { version = ">=1.0.13", features=["full", "extra-traits"]}

On main, this has been changed to:

syn = { version = "1.0.13", features=["full", "extra-traits"]}

But this change has never been published to crates.io.

In fact, a versionize_derive dependency in my Cargo.toml pointing to the main branch is correctly handled by cargo update

versionize_derive = { git = "https://github.com/firecracker-microvm/versionize_derive", branch = "main" }

Is there anything I can do about this on my side, or is this a bug with versionize_derive v0.1.4?