Same same, but different
Nobody has claimed this yet.
- Dominant language
- Macaulay2
- Stars
- 435
- Forks
- 297
- Avg merge
- 4d 20h
- Merged PRs (30d)
- 11
Description
`same` is a... `FunctionClosure` unlike, e.g., `unique` and many others.
`number` is also is the "same" category.
In general, this also relates to the discussion in https://github.com/Macaulay2/M2/issues/1649
We discussed this with @MichaelABurr --- perhaps we should have a default way of declaring exported `Core` methods. Well, first of all, they have to be methods. Also, perhaps `MethodFunctionWithOptions` (created with `Options=>true`) is the way to go --- this would provide flexibility to package developers.
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 with the behavior described for `same`, `FunctionClosure`, `number`, and `unique`, then read the discussion in issue 1649. Investigate how exported `Core` methods and `MethodFunctionWithOptions` are currently handled; done would require an agreed design and corresponding implementation scope.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100