Rationale
Inevitably, we regret some decisions. Fix when the opportunity presents itself.
Plan
- The special ops are not namespace qualified
- should be in clojure ns
- Simplify require/use
Issues
- Wait for new compiler
Labels:
Inevitably, we regret some decisions. Fix when the opportunity presents itself.
2 Comments
Hide/Show CommentsJul 28, 2012
Brandon Bloom
RE: namespace qualified special ops
I found this to be surprising at first:
I expected
I wonder if a top-level letmacro could bind nil, true, and false:
This would allow me to redefine true, false, nil, etc in my own namespace. Or to create a symbol of them without having to call (symbol "nil") etc
Aug 13, 2012
Kevin Downey
This seems that arise from a misunderstanding.
true, false, and nil are not, and have never been symbols. The come out of the reader as nil, and booleans. They are not "special symbols" and eval to nil and booleans.
There also seems to be a misunderstanding of letmacro here