Feature Request: Implement a semaphore
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- rust
- Domain
- operating-systems
Research direction
Start by reading the repository's existing synchronization primitives and platform abstractions to understand its API and portability approach. Define the supported platforms and semaphore behavior first; done means a documented cross-platform inter-process semaphore with coverage for its platform-specific behavior.
Written by the indexing model from the issue text.
Description
Hi,
Thanks to your fundamental works, would you implement a cross-platform semaphore for inter-process communication?
Thanks!
- Dominant language
- Rust
- Stars
- 66
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from elast0ny/raw_sync-rs
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
elast0ny/raw_sync-rs#39 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
elast0ny/raw_sync-rs#30 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
elast0ny/raw_sync-rs#28 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
elast0ny/raw_sync-rs#22 ·
-
Memory lossOpen
Difficulty 4/5 3-5 days Newbie friendliness 25/100
elast0ny/raw_sync-rs#20 ·
All issues in elast0ny/raw_sync-rs
Similar issues
-
good first issue help wanted r-docs
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
servo/rust-smallvec#824 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
priority middle
Difficulty 1/5 Under an hour Newbie friendliness 62/100
KATO-Hiro/AtCoderClans#12940 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
o8 next debug build aborts on Glass to Dark appearance switch (nil identifier messaged before check)Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
hurttlocker/o8#5112 ·