practicalli / practicalli/clojure
Function design - arguments
Open
Nobody has claimed this yet.
design
- Dominant language
- Makefile
- Stars
- 117
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
there are two rules for arg order (coll first, seq last)
Those rules map to -> and ->>.
If you're fighting that, you're probably mixing those styles, which is a smell. https://t.co/GMbXIHlJHp
I have never found a good reason to need as->.
currying is a different functional style and at odds with other design choices in Clojure.
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 files, tests, or entry points are named. First clarify whether this discussion should produce documentation or a concrete design change around argument order, ->, ->>, as->, and currying; done requires an agreed outcome and identified project locations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100