Skip to content

No reason to avoid single-segment namespaces. #100

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

No reason to avoid single-segment namespaces. #100

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 0 additions & 12 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -389,18 +389,6 @@ pairwise constructs as found in e.g. `let` and `cond`.
(:use clojure.zip))
```

* <a name="no-single-segment-namespaces"></a>
Avoid single-segment namespaces.
<sup>[[link](#no-single-segment-namespaces)]</sup>

```Clojure
;; good
(ns example.ns)

;; bad
(ns example)
```

* <a name="namespaces-with-5-segments-max"></a>
Avoid the use of overly long namespaces (i.e., more than 5 segments).
<sup>[[link](#namespaces-with-5-segments-max)]</sup>
Expand Down