Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

make Clojure's performance philosophy re: collections more evident

Open
#223 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
clojure
Domain
documentation

Research direction

Read the existing explanation in the FAQ at clojure.org/guides/faq#conj and compare it with the data structures reference at clojure.org/reference/data_structures. Decide whether the topic needs a short addition or a full guide, covering the collection-performance rationale and its connection to contains? and conj; done means the explanation is clear and appropriately placed.

Written by the indexing model from the issue text.

Description

content

Right now I think this is explained only in the FAQ: https://clojure.org/guides/faq#conj.

Maybe we need a similar sentence or two under data structures: https://clojure.org/reference/data_structures

Or maybe a full-fledged guide that talks in more detail about why this is important, how it motivates both contains? and conj, etc.

Dominant language
HTML
Stars
259
Forks
275
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from clojure/clojure-site

All issues in clojure/clojure-site

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.