More Discriptive Exception Messages
Nobody has claimed this yet.
- Dominant language
- Ada
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Feature request: When an illegal instruction is received (and kills the unit) I think a more descriptive error message should be included. I think this should include at least the operation, the value that is out of range (register A, B, C or the immediate), the value that was provided and the legal values for that argument.
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. Begin by locating the handler for illegal instructions that kill the unit and trace how operation arguments are validated. Done means the exception identifies the operation, offending argument, provided value, and legal values.
Written by the indexing model from the issue text.
Assessment
- Domain
- game-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100