Nice to see that Kotlin gets a proper Path API (currently experimental). I guess I can soon reduce n...

# announcements

[robstoll]

Nice to see that Kotlin gets a proper Path API (currently experimental). I guess I can soon reduce niok (https://github.com/robstoll/niok) to a few extra extension functions 👍

[Vampire]

I certainly hope that was denglish and you meant "get", not "becomes" 😄

[robstoll]

Haha.. indeed, should have written bekomes 😅

[Nir]

Sweet, Kotlin added an operator div!

[Nir]

that's all I wanted 🙂 I was afraid it was going to be one of those things where people were like "uhhh non-intuitive use of operators"

[Nir]

Nevermind that / is a lot more intuitive for path concatenation than "resolve"

[robstoll]

@Nir do you know if one can override / for other purposes? (with operator fun...

[Vampire]

Sure, why not

[Vampire]

It is div

[Vampire]

https://kotlinlang.org/docs/operator-overloading.html#binary-operations

[robstoll]

ah... this one already exists, good to know

[Nir]

Yeah, you can override it however you want. I would say of course, you should use it sparingly 🙂 especiallys ince kotlin has named infix functions, so you don't need the old C++ hack of using operators just ot get infix notation

[Nir]

but for concatenating paths it seems pretty useful since it's the syntax is so pervasive from decades of command line shells

[Nir]

C++ and python have also both adopted / for concatenating paths

[Matteo Mirk]

it seems a nice library, but I can’t find an overview of its extensions without looking at source code: a small documentation would be nice!

[robstoll]

@Matteo Mirk Thanks. I might publish KDoc at some point but I will probably wait to see what functionality I can remove once Kotlin's API for Path is settled.

[Matteo Mirk]

Cool, thanks

[robstoll]

@Matteo Mirk there you go: https://robstoll.github.io/niok/kdoc/ch.tutteli.niok/index.html

[Matteo Mirk]

thank you very much, this is much appreciated! ➕