bkietz commented on pull request #10712: URL: https://github.com/apache/arrow/pull/10712#issuecomment-884326388
> I wonder if there is a way to keep the `enum` (or `enum class`) paradigm and build a separate traits-like mechanism on the side to handle automated conversions/reflection. This is certainly possible, but doesn't reduce the boilerplate as much. Also, IMO the mental overhead of requiring subsequent developers to mimic our `EnumType` declarations is equivalent to that of requiring them to mimic `EnumTraits` specializations -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: github-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
