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

Encapsulate flume::Receiver #1504

Merged
merged 4 commits into from
Oct 7, 2024
Merged

Encapsulate flume::Receiver #1504

merged 4 commits into from
Oct 7, 2024

Conversation

fuzzypixelz
Copy link
Member

@fuzzypixelz fuzzypixelz commented Oct 3, 2024

The entirety of flume::Receiver's API was exposed to anyone who declared subscribers with the default handler (which at least one person, myself). This is arguably not good:

  1. flume could break semver (it seems to be a cool crate but mistakes can happen and you can never be too careful)
  2. Even if flume always respects semver, we can't update it from 0.11 to a semver-incompatible version without break the zenoh API.
  3. We can't change FifoChannel::Handler if a new faster channel comes around.

@fuzzypixelz fuzzypixelz added enhancement Existing things could work better breaking-change Indicates that the issue implies a breaking change (be it at compile time or at runtime) labels Oct 3, 2024
@fuzzypixelz fuzzypixelz self-assigned this Oct 3, 2024
@gabrik
Copy link
Contributor

gabrik commented Oct 3, 2024

The CI is not happy yet :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking-change Indicates that the issue implies a breaking change (be it at compile time or at runtime) enhancement Existing things could work better
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants