Python with a Lissp. https://hissp.rtfd.io Ask, don't ask to ask. Answers may take a day. https://github.com/gilch/hebigo
I think I had also worded it as macros getting quoted arguments in the docs. I should reword that.
Or
%#(+ : :* %) if the function is fixed.
Collection atoms are injections, so they use Python syntax.
There are a lot of examples in the quick start: https://hissp.readthedocs.io/en/latest/lissp_quickstart.html
See the
;;;; COLLECTIONS section.
[\"a\",\"b\"] also works, but single quotes are easier.
You might expect
(list '("a" "b")) to also work, but that has to compile the quotes in to distinguish them from identifiers, resulting in ["('a')", "('b')"].
The right way to do that is
(list `(,"a" ,"b")).
If you're doing anything complicated, like nesting these, or using them in macro templates, the overhead of managing the unquotes and the extra set of parentheses can make this difficult.
In that case, I'd recommend using helper functions.
You could also define an
enset in a very similar way to enlist.
If you'd rather have collections that work more like Clojure, I'd recommend installing pyrsistent and using their helpers.
a minimal example is:
this throws the error
(.upper (let (mystr "asdf")
(operator..add mystr "ghj")))
this doesnt:
(.upper (let (mystr "asdf") (operator..add mystr "ghj")))
great that it is an easy fix
Tabs are allowed in strings, they just aren't whitespace.
Standard tab stops are technically supposed to be equivalent to 8 spaces, when used as indentation. But you more often see them set to 2 or 4, and 1 or 3 is not that rare either. Because indentation is so important for legibility in Lisp, and for Parinfer to work, bad tabstop settings can cause a lot of issues.
so legibility/parainfer, and not something like reader macro clashes or things along those lines
Disallowing them altogether prevents all these issues, and also eliminates a bunch of special cases tooling would otherwise have to deal with.
You can see the regex for tokenizing Lissp in
hissp.reader.
But disallowing tabs for indents was intentional.
I should make the error message clearer, and maybe give it a mention in the docs, since standard practice for most other languages is to treat tabs as whitespace.
i'm still not 100% sold but again i'm pretty indifferent once i change my settings
i understand your reasoning, and maybe it lines up with the forced indenting style of python
but since tooling isnt provided for hissp or default configurations
it does seem like an extra hurdle for new users