Skip to content

Conversation

fko-kuptec
Copy link
Contributor

Upgrades futures-lite to match the PR for async-io-mini.

Open Questions

  • This is a breaking API change. Therefore, at least edge-net would need to be updated to 0.8.0 and edge-nal-std to 0.3.0. However, the latter would then be inconsistent with the versions of the remaining crates.

@ivmarkov
Copy link
Collaborator

Upgrades futures-lite to match the PR for async-io-mini.

Open Questions

  • This is a breaking API change. Therefore, at least edge-net would need to be updated to 0.8.0 and edge-nal-std to 0.3.0. However, the latter would then be inconsistent with the versions of the remaining crates.

As explained here this is not a breaking change, so I'll merge your PR as-is.

Also, once I publish the new version of edge-net on crates.io, most sub-crates' versions would be raised backwards-incompatibly anyway, due to other breaking changes, which had accumulated since the last crates.io release.

@ivmarkov
Copy link
Collaborator

Update: actually you are right, that futures-lite is used as a regular dependency specifically in edge-nal-std, even if this is still an internal detail a bit rather than something which is re-exposed as an API (we just use futures_lite::io::AsyncReadExt/AsyncWriteExt).

Oh well. We'll just raise the version of edge-nal-std as well.

@ivmarkov ivmarkov merged commit 947929d into sysgrok:master Aug 23, 2024
1 check passed
@ivmarkov
Copy link
Collaborator

Actually... edge-nal-std specifically is not released even once yet on crates.io, so whether we'll raise its version (as we did for `async-io-mini) or not - I don't think it matters.

@fko-kuptec
Copy link
Contributor Author

👍

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

Successfully merging this pull request may close these issues.

2 participants