-
Notifications
You must be signed in to change notification settings - Fork 11
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
Interest for #, (comma tuple) tag macro in core? #44
Comments
Seems reasonable. |
It never occurred to me to use a comma. Your post gave me the idea for a Anyway it would be useful for at least me. |
|
But then you have to type (and other's see): |
That seems like a feature. Wouldn't you rather see the same sequence of characters everywhere rather than one in Emacs and something different elsewhere? |
I'm proposing
Usage,
Python3 uses lazy iterators a lot more than Python2 did, so realizing one into a tuple, either for
is something we do really often.
@vodik expressed interest after my initial suggestion at hylang/hy#1545 (comment)
I also noticed @ekaschalk using a
#t
for the same thing in jedhy. I like#,
better, since I think it would be nice to reserve the lowercase single-letter tags for the end user, and our tuple display form(, 1 2 3)
is already using a comma.Is there something else we'd want to use
#,
for?While there are a number of other Python builtins that take an iterable, I don't really think we need a tag macro for the others.
On the other hand, adding the seq abstraction #32 might be a better choice for the use case of re-using a lazy iterator, since a seq is still lazy. But we actually might want to use
#,
to both realize and display a seq in one shot.The text was updated successfully, but these errors were encountered: