Detect and error on unregistered threads
Open
@gapisback is already working on this.
Since Dec 30, 2022.
- Dominant language
- C
- Stars
- 732
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
Just capturing a good suggestion from @ajhconway in https://github.com/vmware/splinterdb/pull/109#pullrequestreview-797942875
User story:
As a developer, I'd like to get a clear and actionable assertion failure or error message if my program were to incorrectly call a SplinterDB function from an unregistered thread, so that I can easily diagnose and fix my mistake.
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.
Assessment
This issue has not been assessed yet.