ruby-concurrency / ruby-concurrency/concurrent-ruby
should we use new c macros included with rubyc?
Open
Nobody has claimed this yet.
enhancement
looking-for-contributor
- Dominant language
- Ruby
- Stars
- 5.8k
- Forks
- 420
- Avg merge
- 20h 45m
- Merged PRs (30d)
- 4
Description
with https://github.com/ruby/ruby/pull/3983 , rubyc includes c macros to do atomic operations. should we use these for the atomic operations?
- Operating system: linux / mac / win
- Ruby implementation: Ruby / JRuby / TruffleRuby / Rubinius
concurrent-rubyversion: x.y.zconcurrent-ruby-extinstalled: yes / noconcurrent-ruby-edgeused: yes / no
Contributor guide
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
Start by reading Ruby PR 3983 and locating the existing atomic-operation implementation in concurrent-ruby-ext. Compare the new rubyc C macros across Linux, macOS, and Windows and consider the listed Ruby implementations; done means a resolved compatibility decision with appropriate coverage if the macros are adopted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, ruby
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100