Improve mesh channels for general-purpose use
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Rust
- Stars
- 1.9k
- Forks
- 238
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 100
Description
Let's make mesh channels more useful, so that we aren't tempted to reach for other channel implementations:
- #596
- Make
mesh_nodeoptional for MPSC channel. - Optimize oneshot channel for single-node use.
- #613
- Remove
'staticandSendbounds on channel elements. - Add a bounded MPSC channel.
- Make bounded MPSC channels work well for RPC.
- Support channels in
no_stdenvironments (by falling back toRc/RefCell).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue is a broad checklist covering mesh channels, MPSC and oneshot channels, RPC, no_std, and channel element bounds. Start by selecting one unchecked item and locating the relevant channel implementation; no file or test is named here. Done means completing that item with appropriate validation, but the issue does not define specific acceptance tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100