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

Mention ^string, ^number in "Type hinting" section

Open
  • Is something wrong?
#316 0 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
55/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Domain
documentation

Research direction

Open content/about/differences.adoc at the “Type hinting” section and compare the current wording with the issue’s cited text. Update the statement so it reflects the added ^string and ^number type hints, then verify the documentation renders correctly.

Written by the indexing model from the issue text.

Description

minor

https://github.com/clojure/clojurescript-site/blob/0ef3da1d56fed6d9de322fed4973f2b17ecf6a9e/content/about/differences.adoc#hinting says:

the only type hint of significance is the ^boolean type hint: It is used to avoid checked if evaluation (which copes with the fact that, for example, 0 and "" are false in JavaScript and true in ClojureScript).

, but that's not true anymore given the ^string, ^number additions.

Dominant language
Shell
Stars
107
Forks
130
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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/clojurescript-site

All issues in clojure/clojurescript-site

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.