Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It was removed without the replacement macro being fully baked, and a number of other things were changed at the same time. Rather than rewrite my stuff at every minor release, I moved on.


That's what I'm asking. What's not fully baked about it? In my (admittedly small) testing, it does its job of assigning stuff in a temporary scope.


I haven’t tried, but are the variables properly captured in closures? LET should have “temporary” lexical scope, not “temporary” temporal/dynamic scope.


It does at least act like it has closures. Try starting the REPL with $ hy --spy and you can see how examples get compiled.


At the time, it just wasn’t there :)

Nowadays it seems to work, but rewriting my code to catch up with today’s version (and cope with the other changes introduced over the last couple of years) is not something I’m interested in doing.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: