linkme VS strum

You can make the code generated by your macro add to a distributed slice from the linkme crate and you can use values from that slice at compile time.

there was linkme which i think can be used for what you describe. from your perspective you get a slice and can put functions in it at link time with an attribute macro.

@dtolnay I noticed you just archived the repos for inventory, linkme, gflags, and typetag, which I assume implies a deprecation.

An alternative to inventory which I find better for a lot of purposes: https://github.com/dtolnay/linkme

I like dtolnay's inventory or linkme crates to register items in a central list, just using decentralized annotations.

Take a look at the strum crate. https://crates.io/crates/strum

I would be use something like https://github.com/Peternator7/strum if I need map string to enum and serde is not the option.

Looks like proper support for this in strum has been proposed.

This crate can generate an iterator for you using a macro https://github.com/Peternator7/strum

The strum crate is also good for removing this kind of boilerplate, and worth checking out!

strum is among my favorite crates to recommend. Favorites of this crate include EnumProperty and EnumIter

I released my first crate that provides a derive macro to easily obtain a name of a current variant in an enum as a string. I did it mostly to learn about procedural macros and the process of releasing a crate. I then found out there is strum which does this and much more. Nonetheless, I learned a lot and I found couple of nice tools like ```cargo-release and git-cliff.

I used https://crates.io/crates/strum to iterate over the enum variants, otherwise you'd have to hardcode the list of variants and wouldn't gain anything.

If you chose to go with the "derive a trait" route the strum crate might be what you're looking for. It lets you use derive to add information about variant count, discriminants or even iterators over variants to an enum.

You might want something like strum