Liking cljdoc? Tell your friends :D


Utilities for collection processing, organised by purpose (or collection type).

Also, for certain error-prone clojure.core functions, drop-in replacements are offered, providing stronger specing (plus type hinting), addressing their error-prone aspects.


[com.nedap.staffing-solutions/utils.collections "2.2.1"]

ns organisation

Everything not under an impl folder or suffix is a public API, and should be concise and optimized for readability.


Please browse the public namespaces, which are documented, speced and tested.


I'd suggest that every function should be heavily speced. That way, consumer projects get a free layer of checking, and type hinting.

clojure.core has a different philosophy (it can return meaningful results for nil arguments, and dubious results for arguments of unexpected type), which is a good idea for a general-purpose language aiming a variety of use cases and styles.

The default namespace is dev. Under it, (refresh) is available, which should give you a basic "Reloaded workflow".

It is recommended that you use ( :after 'formatting-stack.core/format!).


Copyright © Nedap

This program and the accompanying materials are made available under the terms of the Eclipse Public License 2.0.

Can you improve this documentation? These fine people already did:
vemv, Jeroen de Jong, Twan Coenraad, Twan & Lennart Buit
Edit on GitHub

cljdoc is a website building & hosting documentation for Clojure/Script libraries

× close