Fun with C++26 reflection: Keyword Arguments

Re:Fun with C++26 reflection: Keyword Arguments by Gibbon1 on Tuesday February 11, 2025 @01:16AM (#43009572)

Would be happy with a enum that's a named key value.

    key_enum one_two_three 
    {
       FIRST = { .name = "first"},
       SECOND = { .name = "second"},
       THIRD = { .name = "third"},
       LAST = { .value = 255, .name = "last"},
    };

[ Parent | on HN ]

Re:Fun with C++26 reflection: Keyword Arguments by uecker on Tuesday February 11, 2025 @04:02AM (#43010575)

What is wrong with the following? Do you want type more type safety, e.g. linking the enumeration constants to the array?

  enum { FIRST, SECOND, THIRD };
  struct { char *name; int value; } table[] = {
    [FIRST] = { .name = "FIRST", .value = 0 },
    [SECOND] = { .name = "SECOND", .value = 1 },
    [THIRD] = { .name = "THIRD", .value = 3 },
  };

[ Parent | on HN ]

Re:Fun with C++26 reflection: Keyword Arguments by gpderetta on Tuesday February 11, 2025 @06:18AM (#43011518)

You still need generic code to link the enum type to its format string, for example for use in std::format or std::ostream.

Nothing really difficult, normally all of this is done by hand, which is tedious and error prone, or incorporated in a macro. It would just be nice if there was a standard provided turn-key solution to the problem.

[ Parent | on HN ]

Re:Fun with C++26 reflection: Keyword Arguments by jcelerier on Tuesday February 11, 2025 @11:04AM (#43014454)

I have yet to see a project where there have never been bugs due to someone forgetting to update the metadata attached with the enum when there's a change

[ Parent | on HN ]