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
Immutable array wrappers are ubiquitous in JVM ecosystem. These wrappers usually provide different handy methods like content-based equals/hashCode (allowing to use of such wrappers in hash-based data structures), string-like APIs to search for particular values or subsequences within a wrapper, copy or create a subsequence, and so on. Also, these wrappers guarantee that the backing array won’t change, no matter what. The latter allows to overcome the need for defensive array copies.
Okio already has ByteStrings, but these are intermingled with Okio internals. It would be nice to provide an implementation based on Okio ByteStrings, supported by kotlinx-io, but shipped as a different artifact so that users could include it in their projects separately.
The text was updated successfully, but these errors were encountered:
Immutable array wrappers are ubiquitous in JVM ecosystem. These wrappers usually provide different handy methods like content-based equals/hashCode (allowing to use of such wrappers in hash-based data structures), string-like APIs to search for particular values or subsequences within a wrapper, copy or create a subsequence, and so on. Also, these wrappers guarantee that the backing array won’t change, no matter what. The latter allows to overcome the need for defensive array copies.
Okio already has ByteStrings, but these are intermingled with Okio internals. It would be nice to provide an implementation based on Okio ByteStrings, supported by
kotlinx-io
, but shipped as a different artifact so that users could include it in their projects separately.The text was updated successfully, but these errors were encountered: