You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Okio 2 is also making an effort to multiplatform base on kotlin. And the functions provided by core are supported by Okio. So, why not to concern to use Okio to as kotlin-io library? Or, what's the main difference between this library and Okio?
The text was updated successfully, but these errors were encountered:
It would be nice to have a unified effort at building an efficient multiplatform I/O library for Kotlin, unless of course there is a notable difference between the 2 approaches that may suit different needs and would justify 2 I/O libraries.
We're rebooting the kotlinx-io development (see #131), all issues related to the previous versions will be closed. Consider reopening it if the issue remains (or the feature is still missing) in a new version.
Okio 2 is also making an effort to multiplatform base on kotlin. And the functions provided by core are supported by Okio. So, why not to concern to use Okio to as kotlin-io library? Or, what's the main difference between this library and Okio?
The text was updated successfully, but these errors were encountered: