digitalmars.D.learn - A pass() identity range?

bearophile (30/30) Dec 22 2012 I sometimes write code like:

monarch_dodra (8/38) Dec 22 2012 Bug reporting aside, it can be useful in the sense of *doing*
bearophile (4/4) Dec 22 2012 See also:
=?UTF-8?B?QWxpIMOHZWhyZWxp?= (4/6) Dec 22 2012 I liked the idea yesterday but I thought that the name was a little off....

monarch_dodra (3/11) Dec 24 2012 Niiice. I like it.

H. S. Teoh (9/24) Jan 02 2013 This response is a year late ;-) but I thought tee() might be a better

bearophile (6/8) Jan 02 2013 Python programmers have this "tee":

H. S. Teoh (9/15) Jan 02 2013 [...]

D Lark (12/24) Dec 02 2021 Not really, the python itertools.tee affords a sort of 'save' on

Steven Schveighoffer (7/8) Dec 02 2021 Note the date of post you are responding to.

D Lark (6/15) Dec 02 2021 Well, if it should not be possible to reply then maybe disable it
D Lark (5/14) Dec 02 2021 PS: I think this message is unhelpful, unnecessary (since you

Paul Backus (10/12) Dec 02 2021 The function you are looking for is [`std.range.tee`][1].

D Lark (12/24) Dec 02 2021 I had see the std.range.tee, but it does not appear to me to be
D Lark (12/24) Dec 02 2021 I had see the std.range.tee, but it does not appear to me to be

D Lark (9/23) Dec 02 2021 Even in the present day, it seems there still exists a

Mike Parker (14/19) Dec 02 2021 No one has been patronizing to you. They were just explaining the

"bearophile" <bearophileHUGS lycos.com> writes:

I sometimes write code like:

auto data = File("data.txt")
             .byLine()
             .map!(r => r.strip().dup)()
             .filter!(r => !r.empty)()
             .array();


To help writing/improving/debugging such code maybe it's useful 
to create a pass() range in Phobos. It's like a "identity range" 
that just passes its inputs to its output, but also runs a given 
lambda to the items that pass through it (the lambda receives a 
const item, to avoid modifications of the data passing through 
the chain):


auto data = File("data.txt")
             .byLine()
             .pass(r => writeln("A: ", r))
             .map!(r => r.strip().dup)()
             .pass(r => writeln("B: ", r))
             .filter!(r => !r.empty)()
             .array();


This usage of pass() allows to introduce debug prints inside very 
long chains of such iterables, with no need to break them apart 
and assign the parts to temporary variables just to see what's 
going on in that chain.

But it's not hard to do it with a not pure map:

                 .map!((r){ writeln("B: ", r); return r; })()

Or even with an evil comma operator:

                 .map!(r => (writeln("B: ", r), r))()

So I don't know how much useful that pass() is.

Bye,
bearophile

Dec 22 2012

"monarch_dodra" <monarchdodra gmail.com> writes:

On Saturday, 22 December 2012 at 08:55:35 UTC, bearophile wrote:
 I sometimes write code like:

 auto data = File("data.txt")
             .byLine()
             .map!(r => r.strip().dup)()
             .filter!(r => !r.empty)()
             .array();


 To help writing/improving/debugging such code maybe it's useful 
 to create a pass() range in Phobos. It's like a "identity 
 range" that just passes its inputs to its output, but also runs 
 a given lambda to the items that pass through it (the lambda 
 receives a const item, to avoid modifications of the data 
 passing through the chain):


 auto data = File("data.txt")
             .byLine()
             .pass(r => writeln("A: ", r))
             .map!(r => r.strip().dup)()
             .pass(r => writeln("B: ", r))
             .filter!(r => !r.empty)()
             .array();


 This usage of pass() allows to introduce debug prints inside 
 very long chains of such iterables, with no need to break them 
 apart and assign the parts to temporary variables just to see 
 what's going on in that chain.

 But it's not hard to do it with a not pure map:

                 .map!((r){ writeln("B: ", r); return r; })()

 Or even with an evil comma operator:

                 .map!(r => (writeln("B: ", r), r))()

 So I don't know how much useful that pass() is.

 Bye,
 bearophile

Bug reporting aside, it can be useful in the sense of *doing* 
something to each element, as opposed to "call a function and 
re-assign to original element".

This would be especially true for say: Mutating functions that 
return void, or just plain calling member functions.

I think it's a legit request. If anything, *map* could be 
re-implemented in terms of *call*.

Dec 22 2012

"bearophile" <bearophileHUGS lycos.com> writes:

See also:

http://tech.blinemedical.com/debugging-piped-sequences-f/

Bye,
bearophile

Dec 22 2012

=?UTF-8?B?QWxpIMOHZWhyZWxp?= <acehreli yahoo.com> writes:

On 12/22/2012 12:55 AM, bearophile wrote:

 To help writing/improving/debugging such code maybe it's useful to
 create a pass() range in Phobos.

I liked the idea yesterday but I thought that the name was a little off. 
How about a name like tap()? We tap into data as it's flowing through?

Ali

Dec 22 2012

"monarch_dodra" <monarchdodra gmail.com> writes:

On Saturday, 22 December 2012 at 21:21:21 UTC, Ali Çehreli wrote:
 On 12/22/2012 12:55 AM, bearophile wrote:

 To help writing/improving/debugging such code maybe it's

 useful to
 create a pass() range in Phobos.

 I liked the idea yesterday but I thought that the name was a 
 little off.

Ditto.

 How about a name like tap()? We tap into data as it's flowing 
 through?

Niiice. I like it.

Dec 24 2012

"H. S. Teoh" <hsteoh quickfur.ath.cx> writes:

On Mon, Dec 24, 2012 at 02:35:29PM +0100, monarch_dodra wrote:
 On Saturday, 22 December 2012 at 21:21:21 UTC, Ali �ehreli wrote:
On 12/22/2012 12:55 AM, bearophile wrote:

 To help writing/improving/debugging such code maybe it's
 useful to create a pass() range in Phobos.

I liked the idea yesterday but I thought that the name was a
little off.

 
 Ditto.
 
How about a name like tap()? We tap into data as it's flowing
through?

 
 Niiice. I like it.

This response is a year late ;-) but I thought tee() might be a better
name. It has a precedent in the Unix tee command, which copies stdin
into a file and also passes it along to stdout, quite similar to what is
being done here (except that instead of a file it's a
delegate/function).


T

-- 
To err is human; to forgive is not our policy. -- Samuel Adler

Jan 02 2013

"bearophile" <bearophileHUGS lycos.com> writes:

H. S. Teoh:

 This response is a year late ;-)

No problem.


 but I thought tee() might be a better name.

Python programmers have this "tee":

http://docs.python.org/3/library/itertools.html#itertools.tee

Bye,
bearophile

Jan 02 2013

"H. S. Teoh" <hsteoh quickfur.ath.cx> writes:

On Wed, Jan 02, 2013 at 07:19:31PM +0100, bearophile wrote:
 H. S. Teoh:

[...]
but I thought tee() might be a better name.

 
 Python programmers have this "tee":
 
 http://docs.python.org/3/library/itertools.html#itertools.tee

[...]

Hmm. But isn't that just the same as repeatedly calling .save with D's
forward ranges?


T

-- 
If you want to solve a problem, you need to address its root cause, not
just its symptoms. Otherwise it's like treating cancer with Tylenol...

Jan 02 2013