Inline enum values

[lerno]

Possible feature:

enum Foo : inline int
{
   ABC,
   DEF,
   GHJ
}
...
int a = Foo.GHJ; // a is 2

enum Bar : int (inline String name)
{
  XYY = "a",
  XXZ = "b",
  YZZ = "c"
}  
...
String foo = Bar.YZZ; // foo is "c"

[lerno]

Do we want this?

[lerno]

If this is used for C enums, then this would not mean you can do:

enum Foo : { inline int val }
{
   ABC = 4;
 }
 extern void useFoo(Foo f);
 ...
 useFoo(ABC);

Instead you'd have to do

enum Foo : { inline int val }
{
   ABC = 4;
 }
extern void useFoo(int val);
 ...
useFoo(Foo.ABC);

So all it saves is the Foo.ABC.val

[vssukharev]

I love inlined associated values but, as far as I remember, there are some cons of it

[lerno]

Most of those issues are removed when going to from_ordinal ordinal to convert to the ordinal.

[alexveden]

If this is used for C enums, then this would not mean you can do:

Does this mean that enums in C3 are allowed to have gaps, and starting from different order? Duplicate values for different enum items? If it could improve C compatibility, I think it could be beneficial.

[vssukharev]

Does this mean that enums in C3 are allowed to have gaps, and starting from different order? Duplicate values for different enum items? If it could improve C compatibility, I think it could be beneficial.

By design, having gaps in enums wouldn't be possible in C3 as they are like bound to associated values.

[lerno]

Does this mean that enums in C3 are allowed to have gaps, and starting from different order? Duplicate values for different enum items? If it could improve C compatibility, I think it could be beneficial.

No but you could treat them a bit as if they were values with gaps by inlining an associated value.