Re: Library proposal - indexed_array

From: Hadriel Kaplan (hadrielk_at_[hidden])
Date: 2022-06-24 12:46:19

By the way Julien, I was going to suggest something eventually that might be… controversial, but since Richard brought them up I’ll mention it now:

I think this thing should automatically handle more than just Boost.Describe. I think it should try to handle magic_enum and wise_enum’s generated-enum-info too.

That would make it usable by a much broader user base.

If that’s technically challenging to do, then I think you should approach the authors of them and ask to “normalize” whatever needs to be the same, to make them all usable with this.

I don’t know how they’d respond, but it would be really cool if people could start writing things like index_array that supports all of them.

-hadriel

From: Boost <boost-bounces_at_[hidden]> on behalf of Richard Hodges via Boost <boost_at_[hidden]>
Date: Friday, June 24, 2022 at 12:31 AM
To: boost_at_[hidden] List <boost_at_[hidden]>
Cc: Richard Hodges <hodges.r_at_[hidden]>
Subject: Re: [boost] Library proposal - indexed_array
On Fri, 24 Jun 2022 at 02:01, Hadriel Kaplan <hadrielk_at_[hidden]> wrote:

boost.describe, wise_enum etc solve the case where (for example) I wish to
serialise and deserialise my enum value as text. This is useful in the real
world as, for example, it allows me to easily and reliably implement a JSON
communications protocol that contains my enum.