Stephen Berry

Yes, for JSON we serialize the key type in JSON string form. But, it is a bad idea to do this with binary for a number of reasons: - It...

As I think about this more, I think serializing the object key to BEVE and treating it as a BEVE string and then using that as the key would make...

@chfast If your custom type satisfies a general Glaze type (like a string or object) then you may need to specify that you have customized the write/read so that Glaze...

After considering this issue again, I've decided to not support this directly, as the key could be stored in a BEVE string serialized however the developer desires. There are so...

@ZXShady, I really like your implementation, but felt it could use some improvements and tighter integration with the rest of Glaze, so this was an experiment. I just haven't had...

You're totally right that someone can use your library in Glaze right now with something like: ```c++ template struct glz::meta { static constexpr auto values = enchantum::values; static constexpr auto...

@ZXShady, I'm probably going to delete this PR. What would be the aim of your PR?

Thanks so much for your offer, but enum reflection is simple enough that we don't want to bring on a third party dependency. We need to be able to control...

Okay, after giving more thought and seeing your enthusiasm I'm open to utilizing enchantum more directly. If you want to make a pull request I'll over it in detail and...

@ZXShady, after looking at this a bit more I think I've been able to update this pull request to a decent place. So, I don't think we'll rely on enchantum,...