Remove Bidirectional
#234
Labels
part:channels
Affects channels implementation
scope:breaking-change
Breaking change, users will need to update their code
type:enhancement
New feature or enhancement visitble to users
Milestone
Comments
llucax
added
type:enhancement
This was referenced Nov 6, 2023
github-merge-queue bot
pushed a commit
that referenced
this issue
Nov 9, 2023
- Remove `Bidirectional` channel - Remove `Peekable` and associated methods/classes - Don't import `TypeVar`s from other modules - Make all `TypeVar`s private - Split `_base_classes` into `_receiver` and `_sender` - Make channels return the base sender and receiver types - Make channel's sender and receiver implementation private - Don't use aliases for the base sender and receiver classes - Move merge and select symbols to the top level - Move utility receivers to their own public modules - Move nested class out of the parent class Fixes #233, fixes #234.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What's needed?
Using bidirectional channels is not a recommended practice and should not be encouraged by this library.
Proposed solution
Remove
Bidirectional.Use cases
No response
Alternatives and workarounds
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: