Accepting a `Number` instead of a `Double` will ma...
# datascience
t
Accepting a
Number
instead of a
Double
will make the API more flexible and result in less
toDouble()
boilerplate on the client side, and I can move that conversion to the library side. But will this be problematic performance-wise?