Where are API changes proposed for KotlinX IO? Is...
# io
j
Where are API changes proposed for KotlinX IO? Is there a roadmap somewhere? I want to know what parts of the API are considered more stable and which ones aren't, and what major plans exist to overhaul any of the systems.
f
Hey! The most unstable (and unusable, if you'd ask me) part of the API is files and filesystem support. The current plan is to completely rewrite it (https://github.com/Kotlin/kotlinx-io/issues/241). There are some tasks I want to solve before stabilizing the library, the kotlinx-io-stabilization milestone gives some idea on what's left there (https://github.com/Kotlin/kotlinx-io/milestone/5). There's a chance that some niche APIs, like the so-called unsafe API, could be affected by those tasks, but at this moment there are no plans for major overhaul of anything besides the FS support.
j
Thank you! That makes a lot of sense to me. I'm finding the FileSystem/Path separation rather awkward to work with practically, so I'm glad that's not final. Looking at the issues and commits, is this project on hold or low priority right now? I'm making a multiplatform library and I strongly prefer to make it depend on the most official library for its headers, but I'm a little concerned seeing the timestamps of commits and issues.
f
There were a few tasks in other libraries that took my attention away from the
kotlinx-io
, but the library is not abandoned, and I'm planning to return to a more active development this Fall.
j
Oh good! Are the milestone issues that are listed there decided? In other words, if I go implement them, would it help or do the ideas themselves need additional investigation?
f
They are not decided yet, unfortunately. I'll try to explicitly mark issues that only waits to be implemented with "up-for-grubs" or something. Partially, that's a reason why they were not implemented yet.
j
I kind of figured, but that's OK. Just seeing what I can do to help without getting in the way of the decision making.
kodee loving 1