Handle nil values similar to how Clojure does for #63 #64
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This potentially addresses #63. The goal is to make the behavior on
nil
the exact same as nil would be handled with Clojure equivalent functions.The above behavior works like the following:
-><case>-keyword
keyword
nil
-><case>-string
str
""
-><case>-symbol
symbol
IllegalArgumentException
-><case>
identity
nil
I could also see the argument for simply returning
nil
for all of the above instead or if you truly feelnil
is just a bad input, throwingIllegalArgumentException
/NullPointerException
would be fine and still better than anError
. Let me know if you prefer one more than the other and I'm happy to adjust the PR.For reference:
keyword
symbol
str
name