objectionary / objectionary/lints
"Mystery" objects must be prohibited
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14
- Forks
- 39
- Avg merge
- 22h 54m
- Merged PRs (30d)
- 90
Description
Consider this code:
[] > foo
bar 42 > x
Here, the bar doesn't have +alias, and it's not one of org.eolang objects (there are just about 20 of them there). Let's create a lint that would catch such a situation and complain about it (with an error).
Of course, we must not complain about objects that are defined somewhere in the current program. This code is valid:
[] > foo
[t] > bar
bar 42 > x
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 examining the repository's existing XMIR lints and how they report errors. Implement a lint that rejects references to unknown objects, while allowing objects with +alias and objects defined in the current program. Done means the two invalid-reference cases are reported and the local-definition example is accepted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100