-
Notifications
You must be signed in to change notification settings - Fork 370
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
Perplexing keyword behavior in splice #1352
Comments
I think so. The trick is that in Hy, unlike most Lisps, keywords don't evaluate to themselves. They evaluate to strings, not |
HyKeywords are no longer an instances of string with a particular prefix, but a completely separate object. This means keywords no longer trip isinstance str checks, adding a little bit of type safety to the compiler. It also means that HyKeywords evaluate to themselves. Closes hylang#1352
HyKeywords are no longer an instances of string with a particular prefix, but a completely separate object. This means keywords no longer trip isinstance str checks, adding a little bit of type safety to the compiler. It also means that HyKeywords evaluate to themselves. Closes hylang#1352
HyKeywords are no longer an instances of string with a particular prefix, but a completely separate object. This means keywords no longer trip isinstance str checks, adding a little bit of type safety to the compiler. It also means that HyKeywords evaluate to themselves. Closes hylang#1352
HyKeywords are no longer an instances of string with a particular prefix, but a completely separate object. This means keywords no longer trip isinstance str checks, adding a little bit of type safety to the compiler. It also means that HyKeywords evaluate to themselves. Closes hylang#1352
That was strange for a Lisp, but easy enough to understand.
Somehow it became the opposite? Is this how it's supposed to work?
The text was updated successfully, but these errors were encountered: