You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
build(channel): consolidate feature flags and documentation #216
The 0.7 feature and documentation structure is finalized:
Keep oneshot, mpsc, broadcast, and watch as independent opt-in Cargo features matching the public delivery families that are implemented.
Do not add a channel umbrella feature. It would not provide a stable audit, dependency, or compilation boundary beyond enabling unrelated APIs together.
Do not create feature flags for producer topology or bounded versus unbounded policy. Those choices remain visible in module paths and constructors, such as broadcast::mpmc::unbounded and mpsc::bounded.
Keep public modules and source families at direct crate-root paths. Shared implementation machinery remains private under crate::internal when it is genuinely shared.
Document each feature and public module in the README and crate-level API map.
docs: refine 0.7 release documentation #235 is a release-documentation follow-up that makes the shipped channel topology more explicit; it does not change the decision above.
Future aggregate or topology-specific features require a concrete compile-time, dependency, binary-size, or audit boundary and can be proposed independently.
Closing as completed. The final 0.7 decision is to retain independent oneshot, mpsc, broadcast, and watch features, with no channel umbrella and no topology- or capacity-specific feature flags. The issue body now records the outcome and the implementing PRs.
Activity
tisonkun commentedon Aug 29, 2026
Closing as completed. The final 0.7 decision is to retain independent
oneshot,mpsc,broadcast, andwatchfeatures, with nochannelumbrella and no topology- or capacity-specific feature flags. The issue body now records the outcome and the implementing PRs.