use of "nothing" with newRing
Nobody has claimed this yet.
- Dominant language
- Macaulay2
- Stars
- 435
- Forks
- 297
- Avg merge
- 4d 20h
- Merged PRs (30d)
- 11
Description
It would be better to use "null" here:
```
i61 : options newRing
o61 = OptionTable{Constants => nothing }
DegreeLift => nothing
DegreeMap => nothing
DegreeRank => nothing
Degrees => nothing
Global => nothing
Heft => nothing
Inverses => nothing
Join => nothing
Local => nothing
MonomialOrder => nothing
MonomialSize => nothing
SkewCommutative => nothing
VariableBaseName => nothing
Variables => nothing
Weights => nothing
WeylAlgebra => nothing
o61 : OptionTable
```
But there must have been a reason for doing it this way...
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 at the newRing entry point and inspect how OptionTable fields are represented and printed. Check existing tests or documentation for the distinction between null and nothing, then determine whether changing this output preserves option behavior; done means the intended representation is established and covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100