-
Notifications
You must be signed in to change notification settings - Fork 55
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.
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
Should node/coerce also be implemented for nil? #52
Labels
Comments
No, it's perfectly reasonable to implement the protocol for |
Would you accept a pull-request or is it not a thing you'd want in the main code-base? |
@jespera I'll gladly accept a PR for this! Sorry for being kinda vague in the previous comment. :) |
Released as 0.6.0. |
Very nice! Thanks a lot for the quick response. 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If I call
(node/coerce nil)
I get an error: (I've added line-breaks in the error message)However, calling
(parser/parse-string "nil")
returns a node<token: nil>
Is this behavior by design? Would it conflict with anything to extend the
NodeCoerceable
protocol tonil
-values?The text was updated successfully, but these errors were encountered: