`Tuple1SemigroupalOps` methods have different names from other `TupleNSemigroupalOps` classes
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 5.5k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 5
Description
I don't know whether this is a deliberate design decision, but it seems wrong to me: the TupleNSemigroupalOps classes offer a consistent family of methods like mapN and traverseN, but for Tuple1SemigroupalOps these get generated as map and traverse instead. I'd like to be able to work consistently with tuples of any size, including 1, so I think it would make more sense if Tuple1SemigroupalOps (and friends) generated the same mapN/traverseN/etc. methods that are present on all the other TupleNSemigroupalOps classes.
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
Compare the generated Tuple1SemigroupalOps methods with the other TupleNSemigroupalOps classes, focusing on the mapN, traverseN, and related method names described in the issue. Confirm the intended consistent API and inspect the existing generation entry point; done means tuple arity one exposes the same N-suffixed method family as the other arities.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100