practicalli / practicalli/clojure

understanding auto-resolve for keywords

Open
#316 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Makefile
Stars
117
Forks
36
PR merge metrics
No merged PRs in 30d

Description

A comment was made that a qualified keyword that uses auto-resolve will substitute the qualified part of the keyword with the current Clojure namespace

https://clojure.org/guides/weird_characters#autoresolved_keys

Does this help with the issues I had with names as part of banking on clojure?
Is auto-resolving names ever a good idea? Code examples of this?

My current feeling is that auto-resolve is more confusing that helpful.

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.

Research direction

Start with the linked Clojure guide section on auto-resolved keywords and compare it with the questions about qualified names and namespaces. Gather representative code examples that explain when auto-resolving helps or causes confusion. Done means the guide or related documentation clearly answers these questions and addresses the banking-related naming concern.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.