gilch
gilch
```Python >>> import colorama >>> import sys >>> id(sys.stdout) 2198406407512 >>> colorama.init() >>> id(sys.stdout) 2198419631912 >>> colorama.deinit() >>> id(sys.stdout) # back to the original, as expected 2198406407512 >>> colorama.init() >>>...
https://macropy3.readthedocs.io/en/latest/overview.html says, > Note that this means **you cannot use macros in a file that is run directly**, as it will not be passed through the import hooks. Sometimes I...
I can't think of a good reason one would want to import macropy and not actually use any macros. It would prevent the kind of confusion seen in #90. It's...
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...