-
[sphinx.ext.viewcode](https://www.sphinx-doc.org/en/master/usage/extensions/viewcode.html#module-sphinx.ext.viewcode) makes it fairly easy to add links to a source page in the API docs, at least if th…
-
We might need a REPL first. #2. Lissp has doctests.
gilch updated
4 years ago
-
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
- The Lissp ReS…
-
Maybe not a serious problem, but currently Lily's Lissp promt looks like Python's prompt `>>> ` instead of `#> `, and continues with `... ` instead of `#..`. But then the displayed Python prompts have…
gilch updated
3 years ago
-
"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 using them …
-
It's harder to tell what's going on due to the prompts #4, since there's no color after copy and pasting, but the first `>>> ` is Lissp and the second `>>> ` is its Python translation. A one-line inpu…
gilch updated
3 years ago
-
Lily suggests completions for attribute access, but not if it's on a module literal, e.g. `math..t` should pop up a suggestion for `tan tanh tau trunc`, etc. It seems to be suggesting only based on Py…
gilch updated
3 years ago
-
I like the discoverability of the macro namespace. Having it named that is helpful. The first line of a Lissp module is almost always going to use `alias`, `prelude`, or some equivalent macro, and it …
gilch updated
1 month ago
-
Reader macros originally required fully-qualified names. I've since added unqualified names ending in a hash in the `_macro_`, and seem to be using those a lot more.
It's a design goal of Hissp tha…
gilch updated
1 month ago
-
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.