`evaluation.adoc` is inconsistent with current function evaluation semantics
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- documentation
Research direction
Start with content/reference/evaluation.adoc and the CLJ-1206 discussion linked in the issue. Verify the intended behavior of eval for function objects and other objects, then update the wording to distinguish guaranteed self-evaluation, errors, and undefined behavior. Done means the page accurately reflects current semantics.
Written by the indexing model from the issue text.
Description
evaluation.adoc states that "Any object other than those discussed above will evaluate to itself," without mentioning function objects. In CLJ-1206, it was reported that certain function objects cause errors in eval, when nested in a form (and since that bug was opened, several others have independently run into this problem and posted on the mailing list).
A fix for CLJ-1206 was declined, with the prevailing opinion seeming to be that eval should not be applied to non-data-structure'y things. If that's the case, clojure.org/reference/evaluation should probably be updated to correctly describe the semantics of eval, and which "other objects" are guaranteed to evaluate to themselves, versus error, versus trigger undefined behavior.
- Dominant language
- HTML
- Stars
- 259
- Forks
- 275
- PR merge metrics
- No merged PRs in 30d
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.
More from clojure/clojure-site
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
clojure/clojure-site#723 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
clojure/clojure-site#538 · 3 comments ·
-
help wanted
Difficulty 1/5 Under an hour Newbie friendliness 62/100
clojure/clojure-site#386 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 55/100
clojure/clojure-site#715 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
clojure/clojure-site#713 ·
All issues in clojure/clojure-site
Similar issues
-
triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
feature pydanty:is-working
Difficulty 1/5 Under an hour Newbie friendliness 88/100
pydantic/pydantic-ai#8647 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
:watch: Not Triaged dotnet-fsharp/svc
Difficulty 1/5 Under an hour Newbie friendliness 90/100