gomacro VS hy

gomacro added macros and generics several years before generics reached release.

I use https://github.com/cosmos72/gomacro when I want to quickly try some code.

Officially, it's not much scripting friendly, but there are unofficial support to make it a proper scripting option like the gomacro.

If it's a simple program I guess you could use gomacro:https://github.com/cosmos72/gomacro

Thanks to gomacro we can import no standard libraries on the notebook :P

For our use (debugging and running small scripts to update data), gomacro should work well enough, despite being an "almost complete" Go interpreter. This isn't the same as the Python REPL which uses entirely the same code to run, but it should be up to the task.

I keep meaning to play with https://github.com/cosmos72/gomacro

Not exactly the same (doesn't embed into the source like this did), but I believe Hylang[0] is the best Lisp package available for modern Python.

[0] https://github.com/hylang/hy

Isn't that a bit what hy (https://hylang.org/) tries to do ? AIUI it is a lisp interacting directly with the AST of Python, allowing seamless interop: Python modules can be used from hy and vice versa, everything is transparent.

I’ve been keeping loose tabs on this and Hy[1] for a while, but I’ve had some trouble figuring out the major differences between them and the use-cases for either. Would love to see an in-depth comparison in the form of a blog post sometime (though maybe the answer here is to do the research and write one up myself).

1: https://hylang.org

“Python is for scientists. Lisp is for engineers.”

Then what does that make Hy language?

https://hylang.org/

Re Languages with lots of example code and LLM’s

With translators or things like Hy lang, one could get the LLM’s to solve your problem in Python before converting it to another form. Then, you just need a translator. If lacking one, it’s easy to translate by hand.

The practicality of this concept will probably vary by use case. My experiments had GPT doing sketching, implementations, boilerplate, and even porting Python to Rust. A legally-clear LLM trained on multiple languages could probably be fine-tuned to do Python to LISP conversions. If not, Hy might be a stepping stone, too.

You could say so: I've been maintaining the compiler since 2016 ;). Infinitesimal Quest 2 + ε (SQ) exists more to advance Hy than for its own sake.

If you are using Python - you might find Hylang (https://hylang.org) interesting.