Update dependency org.jetbrains.kotlinx:kotlinx-io-core to v0.5.4 #392
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.3.3
->0.5.4
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
Kotlin/kotlinx-io (org.jetbrains.kotlinx:kotlinx-io-core)
v0.5.4
Compare Source
Features
ByteString
conversion to/fromNSData
on Apple platforms #384ByteString
from to/fromByteBuffer
, as well as representingByteString
as a read-onlyByteBuffer
on JVM #387ByteString
factory accepting unsigned bytes #390v0.5.3
Compare Source
Features
braces
library to3.0.3
v0.5.2
Compare Source
Features
Unsafe API method signatures were updated to return number of written/read bytes #360
Note that it's a breaking change as return type is a part of method signature.
However, updated methods are all inline, so in general,
projects depending on libraries that were compiled against the previous version
should not experience binary incompatibility issues after adding a dependency on a never
kotlinx-io
version.Added call-in-place contracts to Unsafe API methods #361
Updated Gradle and some dependencies #353
Improved build scripts #371
Removed the
Buffer.buffer
backing field #366v0.5.1
Compare Source
Bugfixes
v0.5.0
Compare Source
Features
Provided an API allowing direct access to Buffer and Segment internals #135, #166
The API is unsafe, delisted from public docs and requires explicit opt-in. It's recommended to
avoid this API unless you're working on integration with other APIs (like,
java.nio
orio_uring
, for example).Improved the way segment pooling is working on JVM #352
Now sharing a segment won't make an original segment and all its copies recyclable.
Instead, the last remaining copy will be placed back into the pool when recycled.
Segments are no longer allocated or lost when taking or recycling a segment from pool
under a high contention due to concurrent requests.
Size of the segment pool on the JVM could now be statically configured by setting a system property
kotlinx.io.pool.size.bytes
.v0.4.0
Compare Source
Features
v0.3.5
Compare Source
Features
CharSequence
s (Sink.writeString
) #318v0.3.4
Compare Source
Features
linuxArm32Hfp
target #303Source.readCodePointValue
) and write (Sink.writeCodePointValue
)Unicode code point values #307
FileSystem.list
) #222Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.