Revive pull request #1348: "Issue 9882 - Implement a "tee" style InputRange...

...so that a function can be called during a chain of InputRanges."
This unittest is producing stdout output. This is especially bad since the unittest is un-documented, so completely useless.

@MetaLang : Can it be re-written in a way that does not write to stdout, or does it conditionally? Could you write to an output range instead, maybe? By printing to an output range, you can also assert the correct output of your range.

In any case, the printing is disruptive to unit-testing:
https://auto-tester.puremagic.com/pull.ghtml?projectid=1&runid=1127154