hissp
hissp copied to clipboard
gilch
It's Python with a Lissp.
Hissp's repository seems to be several projects rolled into one: - The Sphinx docs, with separate licensing. - API docs - Tutorials - Quick Start - Style Guide - FAQ...
Given the new bundled macros #154 #155, a lot of the FAQ is looking pretty dated. It's also not from actually-asked questions, but anticipated ones. Maybe it's time to get...
`\\.` should be an alias of `QzBSOL_.`, i.e. a module literal. Instead it's read as `QzFULLxSTOP_`. Not sure how that happened, but full stops are handled separately, and this seems...
I could certainly walk through re-implementations of some of the basic macros. Should probably include nested templates, like `defmacro/g`/`defmacro!`. See if we can make the Lisp-2 macro work.
Sphinx puts these in the docs as well. And they're useful for cross references. Doctest where applicable.
"Reader macros" run in the Lissp reader, while "compiler macros" run in the Hissp compiler. Simple, right? Except both of these terms mean something completely different in Common Lisp, so...
Too vague to really be actionable, I know, but first impressions matter, and I feel like it could be better than it is. GitHub markdown is pretty limiting. Most interactivity...
One of the primary goals of Hissp is to have good error messages. There are multiple stages to compilation and errors could happen in any of them, which makes debugging...
100% test coverage doesn't mean that everything is actually tested. I'm not even sure if I've covered all my lines yet. I think the compiler could use a little refactoring,...
Displaying the inner workings of the compiler just adds noise for the end user.