News for hackers. Stuff that matters.
Re:Recombine to avoid naming when naming is hard by king_magic on Monday July 06, 2015 @11:56AM (#9840017)
Yeah, that makes sense. The author's terminology/wording wasn't clear/helpful IMO.

Beyond that, though - the above code looks great - until you need to debug it.

Personally, I'd rather pay a 'naming tax' on things for the sake of readability / debugability over what the original author is shooting for any day.

Re:Recombine to avoid naming when naming is hard by KingMob on Monday July 06, 2015 @12:16PM (#9840185)
The post was for Clojure Gazette, and all Clojure programmers would be familiar with the threading functions.

I have to say, minimizing intermediate holding names makes debugging and writing clear code much easier. 97% of the time, I never miss the "naming tax".

Re:Recombine to avoid naming when naming is hard by mbrock on Monday July 06, 2015 @12:00PM (#9840045)
I haven't needed to debug it very much. Thankfully, it's easy to insert debugging helpers at any stage of the pipeline.
Re:Recombine to avoid naming when naming is hard by king_magic on Monday July 06, 2015 @12:07PM (#9840108)
Interesting, maybe I'm just less familiar with debugging in Haskell.
Re:Recombine to avoid naming when naming is hard by mbrock on Monday July 06, 2015 @12:23PM (#9840228)
This is kind of a special scenario since what's described in the pipeline is already an I/O action, which makes it easy to insert logging anywhere (e.g., a "tap" component that prints its input and output w/ timestamp).

Such pipelines aren't necessarily made up of I/O actions though; they can also be pure computations, which cannot perform side-effects such as logging. In that case, you can still insert debugging helpers, but you might need to be slightly creative. For example, if your pipeline generates a list of values, you could put debugging entries into that list.

Generally, though, the saving grace in such a case is that each component will be a pure transformation, which means that you can easily call it with a test input and inspect the output.

There are some step-by-step debugging tools for Haskell, but I haven't used them, and Haskell programmers mostly seem uninterested in that way of debugging. It doesn't fit very well with Haskell's evaluation model anyway. When I work with Haskell, I just debug in a different way, focusing on verifying correctness of functions and their combinations.

Re:Recombine to avoid naming when naming is hard by codygman on Tuesday July 07, 2015 @02:15AM (#9843877)
> There are some step-by-step debugging tools for Haskell, but I haven't used them, and Haskell programmers mostly seem uninterested in that way of debugging. It doesn't fit very well with Haskell's evaluation model anyway. When I work with Haskell, I just debug in a different way, focusing on verifying correctness of functions and their combinations.

I created hs-scrape[0] to write web scrapers and I frequently use the ghci debugger[1] for step-by-step debugging.

0: https://github.com/codygman/hs-scrape/

1: https://downloads.haskell.org/~ghc/latest/docs/html/users_gu...