-
Notifications
You must be signed in to change notification settings - Fork 673
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Coil 3] Any future idea to migrate to kotlinx-io? #1944
Comments
No plans at the moment. Coil needs Okio's |
Actually it looks like |
Yeah, land it in Coil 4.0 should be a fair choice |
Looks like this'll be a Ktor 4.0 thing as well since it's not currently used in the 3.0 beta release. Coil will also migrate to |
ktor migrated to kotlinx-io in 3.0-beta2, What's our plan? @colinrtwhite |
We failed upgrade ktor without a new coil release. |
Some ByteReadChannel extensions moved to io.ktor.utils.io package, see |
Ktor is going to take kotlinx-io as their fundamental IO library.
https://youtrack.jetbrains.com/issue/KTOR-6030
And kotlinx-io will provide off-heap IO primitive support
Kotlin/kotlinx-io#239
Since platform image decoder is not written with Java/Kotlin (i.e. we will not parse image data within art/jvm heap), transfer them natively will be a good idea
Due to kotlinx-io is under development, I'm not expecting this to be implemented in few weeks(or months?)
The text was updated successfully, but these errors were encountered: