Atomic add with return of new value
Nobody has claimed this yet.
- Dominant language
- Gleam
- Stars
- 6
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
I was rewatching parts of your livestream and realise that add with a return value was headache inducing.
Feel free to close this if it's offtopic. But i thought about rewriting the sequential ID generator in my project with atomics.
Currently I am using an actor for that.
Looking at this module I could use compare_exchange and retry on error but i dont feel like that would be a good use of atomics.
Are you planning to revisit add returning the new value in the future?
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
Start by reading the module's public add operation and its existing atomic operation coverage. Determine whether returning the new value is intended API behavior, then confirm the expected semantics and completion criteria before changing anything; this issue does not name specific files or tests.
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
- 20/100