Improve bignum ECALLs failure reporting
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 44
- Forks
- 7
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 3
Description
Currently, ECALLs for bignums always either return 1, or fail with a panic; either we make them void and have no return value, or we have better error reporting (so some cases might return 0, but not cause panic).
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 bignum ECALL definitions and every caller that depends on their current return value or panic behavior. Clarify whether the intended contract is void calls or explicit failure reporting, then verify that the chosen behavior distinguishes failures without panicking.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100