Kodi Arfer

Sounds like a good idea to me. We were following Clojure here, but Common Lisp's interpretation makes more sense to me.

Actually, if we do that, perhaps we should use Common Lisp's names, `incf` and `decf`, so as not to trip up Clojure programmers.

> there's no equivalent concept in Hy of a "generalized place variable" But there is; it's the same concept of lvalue that Python uses. Just as you can put a...

> I'm betting that `setv` was only called what it was because Python has the built-in `set` function (@Kodiologist confirm?) It looks like it (73695881a9b69bab9d10a356258e78cf0ec6afa3). Yeah, it's not clear how...

@gilch's argument seems even better now that `nil` is gone in place of `None`. That said, I never use `lif` myself, so I can't say I have very strong preferences...

Okay, I think those could be reasonable compromises.

In Rogue TV, I wrote a macro `set-self` that does the same thing as Tuuka's `set-attributes`. The fact that we independently came up with this macro is a hint that...

> I feel like it shouldn't be this hard. Model patterns (#1593) would help. ;) > `HyKeyword`'s `__str__` shouldn't include the colon so I don't have to cut it off...

Currently, `flatten` uses `coll?` to decide whether to flatten something. This example constitutes a good argument that `coll?` isn't the right criterion. But it's not clear what we should use...

By the way, if you just want to concatenate one level of iterables in `x`, without recursive flattening, you can use `(reduce + x)` or `(sum x [])`.