Filipp Zhinkin

An implementation will definitely take different memory types into account, otherwise, it'll be hard to make performant reads/writes.

@rnett, that's correct. Once solved, this issue should allow more easily implementing things like `HashingSink`. I'm currently finalizing the design and will post it soon.

I see a few design options here: - return a list or a sequence (but `Sequence` is not closable); - support filtration by filename or by additional metadata that could...

@SPC-code would something like these work for you? ``` fun String.encodeToAsciiByteString(): ByteString { val bstr = this.encodeToByteString() if (bstr.size != length) throw IllegalArgumentException("String is not an ASCII string: $this") return...

@lppedd could you please elaborate what do you mean under "extended ASCII"?

I believe that such scenarios require explicit encoding routine that will use `Windows-1252` or some other 8-bit encoding. Silently falling back to some default charset encoding is not a great...

@qwwdfsad nice!

We're rebooting the kotlinx-io development (see https://github.com/Kotlin/kotlinx-io/issues/131), all issues related to the previous versions will be closed. Consider reopening it if the issue remains (or the feature is still missing)...

We're rebooting the kotlinx-io development (see https://github.com/Kotlin/kotlinx-io/issues/131), all issues related to the previous versions will be closed. Consider reopening it if the issue remains (or the feature is still missing)...

We're rebooting the kotlinx-io development (see https://github.com/Kotlin/kotlinx-io/issues/131), all issues related to the previous versions will be closed. Consider reopening it if the issue remains (or the feature is still missing)...