2 ms·
The "delaying expensive function calls" part gave me more of a clue than anything. I still have to admit that I don't get the benefit of plumb over existing lam
by smt88 12y ago
The "delaying expensive function calls" part gave me more of a clue than anything. I still have to admit that I don't get the benefit of plumb over existing lambda syntax, and that benefit still would have to be weighed against the additional requirement of learning plumb syntax for someone new to my code base.
I did read "When not to use Plumb" but, from the example, was looking at a single line. I meant that that single line is difficult to look at and say, "My bug isn't in that line."
- chriswarbo 12y agoI originally wrote Plumb for PHP, which has much more cumbersome lambda notation than Python, so the Python port is less useful; it's more for completeness (I'm playing with a Haskell version too, which is even less necessary). Since the main point of Plumb is that its syntax is compatible with other languages, we might as well embed it in anything that works :) As a bonus, the Python version will curry everything you give it. This is nice, since non-curried functions are unnecessarily painful to work with, but you could do that without using Plumb.