Skip to content
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

Compiler warning with using kotlinx.io.IOException #110

Closed
amanjeetsingh150 opened this issue Apr 20, 2020 · 2 comments
Closed

Compiler warning with using kotlinx.io.IOException #110

amanjeetsingh150 opened this issue Apr 20, 2020 · 2 comments

Comments

@amanjeetsingh150
Copy link

amanjeetsingh150 commented Apr 20, 2020

I striked while usage of kotlinx.io.IOException with this following compiler warning while doing some multiplatform I/O operations:

Screenshot 2020-04-20 at 7 42 10 AM

Writing the text if you are not able to read: Using exception is an error. these classes accidentally slipped to the public api surface. We neither had intent to provide a production-quality implementation nor have an intent to support them. They are removed and to migrate, you can either use a corresponding java.io type or just a copy-paste implementation from the GitHub. If you have a use-case for multiplatform IO, please report it to the https://github.com/Kotlin/kotlinx-io/issues

Have used the Github Implementation of IOException. But wanted to know what exactly happened are we not suppose to get it for this version or it will be available for future?

Currently have used the Github Implementation of IOException.

@Ktlo
Copy link

Ktlo commented Apr 28, 2020

The same issue happened to me when I used org.jetbrains.kotlinx:kotlinx-serialization-runtime dependency. Kotlinx Serialization library also has kotlinx.io.IOException type alias and it's deprecated there. Maybe you have this dependency too.

@fzhinkin
Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants