Hello Rich,

I noticed a difference between boot.clj and the API Docs. I know that
there are internal definitions, which are not supposed to be used by the
user. New functions might also take some time, before they show up in
the docs.

But I'm missing for example delay and force. I found myself implementing
a Promise class to do exactly this! While working on VimClojure I found out by accident that there is a force and hence a delay. That could have saved
me some time...

I understand that you don't want the docs to be open for public editing.
But maybe we can install a process so that people can easily access the
source for the docs (eg. via SVN repo), write a patch and submit it to
you. You can review it and push it finally to the website if you agree
or request changes or reject the patch completely.

This would be a compromise between you doing all the work and public
editing. (And it would free some time for you to concentrate on Clojure
itself. :))

I think clojure.org should stay a moderated and authoritative resource
for the docs. But it should be up-to-date even when the available
functions still change.

Just some thoughts...

Sincerely
Meikel

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to