Jolan Rensen

Long story short: We may need to bump to Gradle 9.x to be able to use nested type aliases from KoDEx

https://github.com/Kotlin/dokka/pull/4261 Dokka merged nested type alias support :) it's only a matter of time before we'll be able to use them

I bumped KoDEx https://github.com/Jolanrensen/KoDEx/releases/tag/v0.5.0 to Dokka 2.1.0, meaning we can now bump to KoDEx 0.5.0 and start using nested type aliases to hold KDocs

To show how effective this is: Before: After: And inside the jar itself:

Kotlin 2.3 stabilizes nested type aliases, so when it's released we can do this.

[temporary_workaround_fix_for_#1116_in_notebooks.patch](https://github.com/user-attachments/files/23747697/temporary_workaround_fix_for_.1116_in_notebooks.patch) new up-to-date patch file

[llms.txt](https://github.com/user-attachments/files/24036279/llms.txt) this is what it spits out :) While it looks rather complete, I am not sure if it may be too large for users to include in their context......

Maybe we can put a note about this in the compiler plugin docs on the website :) and then link to it from our documentation about using dataframe on android

I like this approach too. It's much easier to support from a compiler plugin (compared to `(@Import DataFrame.read(""))`), since annotations rely solely on constants anyway. We would need to try...

Good idea! We use a similar algorithm for quick select in our percentile/median/quantile implementation: https://github.com/Kotlin/dataframe/blob/b46524691922c1c49c5258b2f74d7ac8aa817c85/core/src/main/kotlin/org/jetbrains/kotlinx/dataframe/math/quantile.kt#L281 though this only returns a single element. According to the [TopKSelect source](https://fossies.org/dox/guava-33.4.8/android_2guava_2src_2com_2google_2common_2collect_2TopKSelector_8java_source.html) their solution uses...