www.digitalmars.com         C & C++   DMDScript  

digitalmars.D - More fun with std.range.transposed

reply "H. S. Teoh" <hsteoh quickfur.ath.cx> writes:
http://d.puremagic.com/issues/show_bug.cgi?id=9507

Thoughts?


T

-- 
The only difference between male factor and malefactor is just a little
emptiness inside.
Feb 13 2013
parent reply "monarch_dodra" <monarchdodra gmail.com> writes:
On Wednesday, 13 February 2013 at 21:34:27 UTC, H. S. Teoh wrote:
 http://d.puremagic.com/issues/show_bug.cgi?id=9507

 Thoughts?


 T

Just a quick question: Isn't "Transverse" conceptually the same as a "range of FrontTraversal" ? I'd say you have two options: 1) Simply statically enforce "EnforceNotJagged": This would make more sense (IMO) given the definition of "Transverse". You could enforce it via asserts. 2) Just like FrontTraversal, allow an option parameter.
Feb 13 2013
parent "H. S. Teoh" <hsteoh quickfur.ath.cx> writes:
On Wed, Feb 13, 2013 at 11:07:30PM +0100, monarch_dodra wrote:
 On Wednesday, 13 February 2013 at 21:34:27 UTC, H. S. Teoh wrote:
http://d.puremagic.com/issues/show_bug.cgi?id=9507

Thoughts?


T

Just a quick question: Isn't "Transverse" conceptually the same as a "range of FrontTraversal" ?

I suppose you could regard it that way. It's a range of frontTransversal where popFront pops the front element of each subrange.
 I'd say you have two options:
 1) Simply statically enforce "EnforceNotJagged": This would make
 more sense (IMO) given the definition of "Transverse". You could
 enforce it via asserts.
 
 2) Just like FrontTraversal, allow an option parameter.

Yes, the question is, which option should be implemented? Or should that be a compile-time parameter? T -- Gone Chopin. Bach in a minuet.
Feb 13 2013