Thread safety
Nobody has claimed this yet.
- Dominant language
- Macaulay2
- Stars
- 435
- Forks
- 297
- Avg merge
- 4d 20h
- Merged PRs (30d)
- 11
Description
Some of our code and many of our third party libraries are not thread safe, and some of those that are,
such as mpfr, achieve thread safety in a way that makes our use of libgc break,
by storing libgc pointers in thread local variables in locations unknown to the libgc
garbage collector.
A long term project is to make everything thread safe.
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 no files, tests, or entry points. Start by investigating how libgc interacts with thread-local pointers and the use of third-party libraries such as mpfr. The issue describes a long-term goal, but does not define a bounded change or a concrete completion test.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100