Code Observation: Clojure's Destructuring

#1

Post by semperos » Mon, Jun 14, 2021, 11:08 AM UTC

Code Observation: Clojure's Destructuring
danielgregoire.dev

Re: Code Observation: Clojure's Destructuring

#2

Post by macintux » Mon, Jun 14, 2021, 2:28 PM UTC

This functionality in Erlang is something I miss in most other languages, and I was quite displeased when I discovered Python 3 abandoned tuple destructuring in function invocations.

Re: Code Observation: Clojure's Destructuring

#3

Post by lmilcin » Mon, Jun 14, 2021, 2:46 PM UTC

macintux wrote: post #2

This functionality in Erlang is something I miss in most other languages, and I was quite displeased when I discovered Python 3 abandoned tuple destructuring in function invocations.

I don't know Erlang but I also found Clojure's destructuring to be an extremely useful tool. For me it allowed developing useful project idioms that can be very effective in cutting a lot of boilerplate.

Re: Code Observation: Clojure's Destructuring

#4

Post by whalesalad » Mon, Jun 14, 2021, 3:37 PM UTC

macintux wrote: post #2

This functionality in Erlang is something I miss in most other languages, and I was quite displeased when I discovered Python 3 abandoned tuple destructuring in function invocations.

The destructuring abilities of Javascript are something I regularly miss in Python, especially when I am hacking on a polyglot project with a JS frontend and a Py backend.

Re: Code Observation: Clojure's Destructuring

#5

Post by eatonphil » Mon, Jun 14, 2021, 6:24 PM UTC

Interesting use of to show the results of a computation. I missed the explanation in the beginning that said the results were precomputed. I thought clicking it was running. Format-wise since it's not actually running when clicked, I'm not sure hiding the result behind is much clearer than just including the result as displayed by the REPL in the same snippet.

Re: Code Observation: Clojure's Destructuring

#6

Post by Fellshard » Mon, Jun 14, 2021, 7:52 PM UTC

eatonphil wrote: post #5

Interesting use of to show the results of a computation. I missed the explanation in the beginning that said the results were precomputed. I thought clicking it was running. Format-wise since it's not actually running when clicked, I'm not sure hiding the result behind is much clearer than just including the result as displayed by the REPL in the same snippet.

As a flipside argument, it may be useful in an article like this to help people test their own intuition on what a piece of code will do.

Re: Code Observation: Clojure's Destructuring

#7

Post by davidwf » Mon, Jun 14, 2021, 11:15 PM UTC

Really great in-depth article! At this point in my life I feel like there's such a large amount of content for "beginners" written by people who have only been coding for five years, and a huge dearth of "intermediate" content for people who are adults, and who do know how to code, but who would benefit from being walked through the deeper parts of the language, and this article really fits into that sweet spot for me.

Re: Code Observation: Clojure's Destructuring

#8

Post by nerdponx » Tue, Jun 15, 2021, 4:10 AM UTC

eatonphil wrote: post #5

Interesting use of to show the results of a computation. I missed the explanation in the beginning that said the results were precomputed. I thought clicking it was running. Format-wise since it's not actually running when clicked, I'm not sure hiding the result behind is much clearer than just including the result as displayed by the REPL in the same snippet.

My only complaint is that the icon looks like the "play" icon. Otherwise, I like it.