rusterlium / rusterlium/rustler
Redo error handling
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 4.9k
- Forks
- 246
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 7
Description
I am not happy with the way NifError works at the moment. It should be revised/improved and integrated with already written code.
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 locating the existing NifError implementation and the already written code it is expected to integrate with. Review the current error-handling flow and determine the intended revised behavior before changing anything. Done means NifError is coherently revised and integrated throughout the relevant existing code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- erlang, rust
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100