Whether this is “counter-intuitive” or not is a matter of opinion (to me it’s perfectly logical) but it is certainly not unexpected (because that’s how the JVM specifies it.) I suspect the issue author does not work in realms where Byte and Short are used very much (byte and bit manipulation is an area where Kotlin is still somewhat deficient in general.) I hope these patterns continue to gain traction and help make Kotlin a platform for data science.I don’t see how this deprecation helps - the suggested replacement: val double = 129.0 What started as an experiment to see if Kotlin could be idiomatic for analytical tasks ended up becoming much more than I anticipated. Thank you for the enthusiastic support and usage of this library. 👀 If you have any ideas, please contribute and I'll be happy to consider adding features. I'll conservatively expand on these non-statistical features possibly, but I may spin off other projects.

There are a few exceptions I've decided to keep, such as clustering and linear regression. I've decided to focus this library primarily on statistics, and steer away from linear algebra and other data science tasks.

✅ Unit tests have been written for approximately 96% of the codebase.👀 Many higher order function parameters have been renamed.Most operators have been consolidated to target Number, rather than overloads for every numeric input type.Maven artifact is now called kotlin-statistics, not kotlinstatistics.There have been some major refactorings from the pre-1.0 versions. 🚀 I'm excited to announce that I've settled on a base set of features and released Kotlin-Statistics 1.0.

Kotlin double range