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

Consider moving core IO primitives to the standard library prior to their stabilization #354

Open
qwwdfsad opened this issue Jul 12, 2024 · 0 comments

Comments

@qwwdfsad
Copy link
Member

qwwdfsad commented Jul 12, 2024

With Kotlin being more and more standalone ecosystem, especially in the face of the multiplatform adoption, it would be nice to start moving towards a unified out-of-the-box experience for the core Kotlin functionality.

IO primitives are the unified and common layer for the applications and libraries, and having them in a separate library with its own release cycle and Kotlin compatibility matrix is just an additional burden for the users, esp. taking into account that we do not expect much of changes there after the stabilization. It would be nice to see core primitives (ByteString, Sink, Source, Buffer) in the standard library, leaving kotlinx-io as the additional extensions and fast-paced library for new-coming APIs (filesystems, processes, encodings).

Apart from technical and operational peculiarities, one of the biggest questions for this change is whether we are willing to tolerate unsafe API in the standard library, as it potentially hinders the platform integrity

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

No branches or pull requests

2 participants