From a95f801ce7ca235d26046e2cac76e882ea6003e6 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Alejandro=20Gonz=C3=A1lez?= Date: Sun, 2 Oct 2022 15:58:33 +0200 Subject: [PATCH] Update darling crate to 0.14.x A semver-breaking version of the darling crate was released just a few days after the last release of enumset, and other crates of the Rust ecosystem, such as serde_with, have moved to the newer version. Even though enumset works just fine anyway, it is a good idea to update because that way Cargo doesn't need to download and build two different versions of the same crate for the same application, which negatively impacts the executable size. Moreover, some automated analysis tools such as `cargo deny` rightfully warn about this condition. This commit just bumps the darling version to the latest one. I've looked at the darling changelog and I don't think that enumset is impacted by any breaking changes. To confirm this, I've successfully run the test suite with `cargo test`. --- enumset_derive/Cargo.toml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/enumset_derive/Cargo.toml b/enumset_derive/Cargo.toml index 39648c8..6dd572a 100644 --- a/enumset_derive/Cargo.toml +++ b/enumset_derive/Cargo.toml @@ -18,7 +18,7 @@ proc-macro = true serde = [] [dependencies] -darling = { version = "0.13.0", default-features = false } +darling = { version = "0.14.1", default-features = false } syn = "1" quote = "1" proc-macro2 = "1" -- 2.44.0