<div dir="ltr"><div dir="ltr">On Wed, Oct 16, 2024 at 8:33 PM Archie Cobbs <<a href="mailto:archie.cobbs@gmail.com">archie.cobbs@gmail.com</a>> wrote:</div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr">On Wed, Oct 16, 2024 at 7:09 PM David Alayachew <<a href="mailto:davidalayachew@gmail.com" target="_blank">davidalayachew@gmail.com</a>> wrote:</div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">Now, to my question -- are there any downsides or obstacles to adding Enum.name() to this list of constant expressions?</div></blockquote><div><br></div><div>Just to clarify, this could only work for enum constant literals, e.g., <span style="font-family:monospace">FOOBAR.name()</span> which would obviously have value <span style="font-family:monospace">"foobar"</span>.</div></div></div></blockquote><div><br></div><div>Oops, I meant "FOOBAR" ...</div></div><div class="gmail_quote"><br clear="all"></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature">Archie L. Cobbs<br></div></div>