gilch

> Maybe the solution is a another [`apply`] version with different ordering. On second thought, you can use a `->>` anywhere in a `->` to thread in the tail for...

I just realized that the `as->` macro works even without `apply`. ```Hy => (-> (range 10) iter , (* 2) (as-> it (zip #* it)) list) ``` ```Python it =...

> a new HyModel type ... the compiler's job to join Exactly what I was thinking.

First, a quick demonstration of dynamic variables in Emacs Lisp, so we're on the same page: ``` Elisp ELISP> (defun greet () (format "Hello, %s!" the-name)) greet ELISP> (defvar the-name...

> But I'm not completely sure if I understand (or even can think of) all possible cases for this. Variables with dynamic scope would only be available inside a let...

Something as simple as ```Hy (import pyrsistent) (defreader p [form] `(pyrsistent.freeze ~form) ) ``` would get us pretty far. That's enough for `PVector` `PMap` and `PSet`. The `freeze` function is...

The interface seems basically the same, but I think PVector/PSet share data between revisions in a [trie](https://en.wikipedia.org/wiki/Trie) like Clojure does. I'm pretty sure Python's tuple and frozenset implementations don't do...

Perhaps we should put this in extra with an optional dependency for Pyrsistent. This would keep Hy's core install smaller.

What happens if you have dicts/maps * `{:keys [1 2 3]}` and * `{:a 1 :b 2 :c 3}`? In Clojure, you can destructure the former as * `{[a b...

For maximum flexibility, a macro has to be able to interpret a keyword as as keyword instead of a kwarg pair. This way you can write macros that contain keywords...