Arc Forumnew | comments | leaders | submitlogin
2 points by eds 6149 days ago | link | parent

There was a post a while ago about a form of let that managed to mix both multiple assignments and implicit progn behavior, although if I recall correctly it had problems with destructuring binds.

  (let var1 expr1
       var2 expr2
       ...
       (form1 ...)
       (form2 ...)
  )
http://rondam.blogspot.com/2008/02/z-shrtr-bttr.html

The post in question was actually about conciseness as a metric, and the example used in his argument was exaggerated to make his point, but the form he created (the modified let) might actually be useful (although the last stage of his example was a little scary... maybe we shouldn't take it all the way).



5 points by aidenn0 6149 days ago | link

I don't think mixing the two is good. I think the lack of implicit progn would be a Good Thing. The explicit progn makes non-functional code stand out, and it also makes the language a bit more uniform if no primitives have implicit progn. All other things being equal uniformity is good because it reduces surprises. Unless there are a lot of people who feel like the implicit progn is an important part of "let" I'd prefer to not have it.

-----

1 point by bOR_ 6065 days ago | link

nice link, and he makes some good points on keeping away from uberbrevity. Maybe we should let and with rest ;).

-----