practicalli / practicalli/clojure
errors: explain terms used in clojure error output
Open
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 117
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
Explain the language that clojure uses in its error reporting
Examples
- ctor - class constructor - tried to create a new object from a class using its constructor method but didnt find it or has incorrect arguments - may have tried to invoke a constructor on a function rather than a class
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.
Research direction
No file or test is identified in the issue. Start by reviewing Clojure error output and the terminology around the provided “ctor” example. Done means documenting the relevant error-reporting terms clearly, with accurate explanations and an agreed scope for which terms to cover.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100