-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
ARROW-3680: [Go] implement Float16 array #4083
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.
thanks for tackling this!
ping? |
Codecov Report
@@ Coverage Diff @@
## master #4083 +/- ##
===========================================
- Coverage 87.91% 71.83% -16.08%
===========================================
Files 739 74 -665
Lines 90980 6072 -84908
Branches 1252 0 -1252
===========================================
- Hits 79985 4362 -75623
+ Misses 10876 1476 -9400
- Partials 119 234 +115
Continue to review full report at Codecov.
|
Done, let me know any other refactoring I can make, then I will focus on adding more unit tests. |
ping? |
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.
apologies for the belated review.
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.
I'd like to remove the float16.Float16
stutter if possible. Looking for suggestions or ideas
go/arrow/float16/float16.go
Outdated
"math" | ||
) | ||
|
||
type Float16 uint16 |
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.
actually, independantly of how one would call that type, I would perhaps change its definition to:
type Float16 struct { v uint16 }
to prevent mistakes such as:
var v float16.Float16 = 3 // oops... this compiles. it shouldn't.
How is it going with this patch? |
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.
I will make the change accordingly.
ping? (it'd be great to have this in 0.14 and have this in sooner than later so I can update the IPC code to handle |
done |
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.
LGTM modulo my very last nit-picks (promised!)
thanks again.
Done. Thank you for all the suggestion! I learnt a lot. |
(travis failure unrelated) well, thank you for being so tenacious :) |
No description provided.