Wrong dependencies in Readme

[mipastgt]

The build descriptions in the Readme seem to be wrong.

According to my experiments it is not enough to just specify this dependency

implementation("org.jetbrains.kotlinx:kotlinx-io:0.2.0")

for a multiplatform project. It results in

Execution failed for task ':shared:compileKotlinDesktop'.
> Could not resolve all files for configuration ':shared:desktopCompileClasspath'.
   > Could not find org.jetbrains.kotlinx:kotlinx-io:0.2.0.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/org/jetbrains/kotlinx/kotlinx-io/0.2.0/kotlinx-io-0.2.0.pom
       - https://repo.maven.apache.org/maven2/org/jetbrains/kotlinx/kotlinx-io/0.2.0/kotlinx-io-0.2.0.pom
       - https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/kotlinx/kotlinx-io/0.2.0/kotlinx-io-0.2.0.pom
       - file:/Users/mpaus/.m2/repository/org/jetbrains/kotlinx/kotlinx-io/0.2.0/kotlinx-io-0.2.0.pom
     Required by:
         project :shared

Instead you have to specify both modules explicitly like:

    implementation("org.jetbrains.kotlinx:kotlinx-io-core:0.2.0")
    implementation("org.jetbrains.kotlinx:kotlinx-io-bytestring:0.2.0")

This should be made clear in the Readme.

[fzhinkin]

@mipastgt, thanks for spotting and reporting the issue!

Do you experience any issues when only the kotlinx-io-core dependency is specified (I mean, only implementation("org.jetbrains.kotlinx:kotlinx-io-core:0.2.0"), without bytestring)?

[whyoleg]

I've played a little with kotlinx-io, and if to declare only dependency to kotlinx-io-core - overall it works, but you can not create ByteString instances (and overall access ByteString type)
Also readByteString fails on JVM but not on JS/Native

[mipastgt]

Exactly. Everything in kotlinx.io.bytestring is not visible. Tried it on desktop.

[ilya-g]

It's likely because kotlinx-io-core declares a dependency on kotlinx-io-bytestring as implementation, whereas it should be api because it exposes ByteString in its public API.

[ilya-g]

@fzhinkin If you change the dependency type, as #169 proposes, I believe we should not require specifying bytestring dependency explicitly in the readme.

[fzhinkin]

@mipastgt @whyoleg thank you! I updated the README for now, and will solve the issue with explicit bytestring dependency in #169

[fzhinkin]

@ilya-g yeap, thanks! Already working on it.