Make C-extension Ractor-safe
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 13
- Forks
- 10
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 2
Description
In planning ahead to the near future when TruffleRuby can run C-extensions marked with rb_ext_ractor_safe(true) in parallel, and for when Ractors are no longer just experimental, it would be great if the C-extension could be made Ractor-safe, or marked as such if it already is so! Would be happy to send in a PR in the later case.
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 names only the C extension and rb_ext_ractor_safe(true); no files or tests are specified. Start by locating the extension's native entry points and reviewing Ruby's Ractor-safety requirements, then determine whether it can be safely marked or needs broader changes; done means the extension is demonstrably Ractor-safe.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, ruby
- Domain
- operating-systems
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100