-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change scoped enums behavior #309
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I like this approach; the failing tests are probably because we need to update the usages in the Arrow package itself
I will to find time for that within a couple of days. But before I do so, should we reconsider the name of the primitive type, i.e. something other than with leading underscore? I just saw the announcement of enumx.jl https://discourse.julialang.org/t/ann-enumx-jl-improved-enums-for-julia/78096 , which has implemented a similar idea, but using |
On second thought that edit: |
Codecov Report
@@ Coverage Diff @@
## main #309 +/- ##
=======================================
Coverage 87.15% 87.15%
=======================================
Files 26 26
Lines 3301 3301
=======================================
Hits 2877 2877
Misses 424 424
Continue to review full report at Codecov.
|
@quinnj Took me some time to update all usages of the enums in the package, but I got all tests to pass now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I think this is a good correction; thanks @jonalm. The T.__TYPE__
isn't ideal, but I think it's a decent solution.
I went ahead and rebased |
@quinnj Is there something blocking getting this into main? |
Would it be possible to replace the custom implementation of scoped enums here with a dependency on EnumX? That has no dependencies and is very small. |
Sorry all that this languished; I've since become more familiar w/ the EnumX.jl package and agree it's the right way to go. I'll try to do a PR soon switching over to use it. Sorry @jonalm for all the headache here, but thanks for all the help along the way! |
Implement suggestions for #308