kotlinx-io
kotlinx-io copied to clipboard
Kotlin
Kotlin multiplatform I/O library
I am trying to migrate Krossbow, my STOMP-over-websocket multiplatform library, and I stumbled upon this function becoming private/internal in `kotlinx-io`. I [relied on it](https://github.com/joffrey-bion/krossbow/blob/b58ece61db5007c89f0503b58d58a28ada22958b/krossbow-websocket-core/src/commonMain/kotlin/org/hildan/krossbow/websocket/WebSocketCloseReasonUtils.kt#L26-L31) because I need to truncate a...
``` adb shell /data/local/tmp/test.kexe --ktest_regex_filter=kotlinx.io.files.SmokeFileTest.resolve [==========] Running 1 tests from 22 test cases. [----------] Global test environment set-up. [----------] 1 tests from kotlinx.io.files.SmokeFileTest [ RUN ] kotlinx.io.files.SmokeFileTest.resolve kotlinx.io.IOException: mkdir failed:...
There's no FS support for Wasm, although it could be implemented on top of the WASI.
The ability to work with files and filesystems is one of the crucial features that a programming language could provide through its standard library. Even if an application is not...
Sinks and sources created for files using `FileSystem.sink` and `FileSystem.source` may or may not throw an exception on close failure, depending on the platform. For instance, on native platforms `close(fd)`...
At the moment, when receiving data from a mutable `CharSequence`, one has to use `sink.writeString(chars.toString())`, which may be inefficient (copying data to create a `String`, just to then encode it...
There are several cases in binary parsing, where one needs to wrap a `ByteArray` with an interface like `Source` and read from it sequentially. It should be possible by using...
Getting a file's canonical path is one of the few file APIs my library tests require that `kotlinx-io` doesn't currently support. Similar API references: * [JVM File.getCanonicalPath](https://docs.oracle.com/javase/8/docs/api/java/io/File.html#getCanonicalPath--) * [Apple Foundation...
`java.nio.ByteBuffer` is THE data container in Java NIO APIs. Those who need to use features provided only by the NIO APIs (like non-blocking sockets) are doomed to use `ByteBuffer` for...
`SystemPathSeparator` is defined in `nativeMain`
