Our great sponsors
-
variant_common_data
Discontinued A proc macro that generates a convenience struct with all boilerplate for you when you want to declare an enum with some common data between variants (WIP)
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Here's something I came up with quickly. https://github.com/TukanoiddExperiments/variant_common_data. It's not perfect, can be improved a lot (feedback & PRs always welcome! I intend to use this crate myself in the future, since I've had to deal with this issue quite a few times). For now, it's gonna stay in my sandbox workspace before it's ready for 0.1.0 crates.io release. Also, I'm very bad at naming, so ideas on that front are also welcome! I already have some ideas regarding additional features and error handling improvements, but I'd like to hear other peoples thoughts on what I should use/switch to for better compile times, I don't write proc macros very often, so my knowledge on the proc macro crate ecosystem/idiomatic way to parse things/etc might be outdated.
Here's something I came up with quickly. https://github.com/TukanoiddExperiments/variant_common_data. It's not perfect, can be improved a lot (feedback & PRs always welcome! I intend to use this crate myself in the future, since I've had to deal with this issue quite a few times). For now, it's gonna stay in my sandbox workspace before it's ready for 0.1.0 crates.io release. Also, I'm very bad at naming, so ideas on that front are also welcome! I already have some ideas regarding additional features and error handling improvements, but I'd like to hear other peoples thoughts on what I should use/switch to for better compile times, I don't write proc macros very often, so my knowledge on the proc macro crate ecosystem/idiomatic way to parse things/etc might be outdated.