RFC: naming for FrontTransversal and Transversal ranges

[Robert Jacques]

On Sat, 02 May 2009 17:45:16 -0400, Andrei Alexandrescu  
<SeeWebsiteForEmail at erdani.org> wrote:

> Robert Jacques wrote:
>> On Sat, 02 May 2009 10:18:41 -0400, Andrei Alexandrescu  
>> <SeeWebsiteForEmail at erdani.org> wrote:
>>> Bill Baxter wrote:
>>>> On Fri, May 1, 2009 at 6:25 PM, Andrei Alexandrescu
>>>>>  Matrix a, b, c; ... c = a; a += b;
>>>>>  Does the last operation mutate c as well?
>>>>  I said "assignments like a = b are rare" and you put one of those in  
>>>> your example.
>>>
>>> You said it and I don't buy it one femtosecond. Code does need to copy
>>> values around. It's a fundamental operation!
>>  Andrei, he said that explicit assignments/copies of arrays/containers  
>> are rare in numeric computing, which I agree with. Just because it's a  
>> fundamental operation doesn't mean it gets used much is his (or I guess  
>> Numply's actually) specific applications. Also,  
>> disregarding/disbelieving a use case is not helpful to this discussion.
>
> He said something. That's about as much proof as was seen. I didn't buy  
> it so I replied without assuming the same as him. Then he repeated "but  
> I said that!" which upped the ante from supposition to presupposition. I  
> think presuppositions are particularly pernicious so I felt the need to  
> explicitly say that I don't believe it just because he said it. It's not  
> a use case. It's just something that was said. If some sort of evidence  
> is given, that would be great. Don't put the onus on me to disprove what  
> was said.
>

I don't expect you to disprove what was said. I would hope that when you  
see someone over-generalizing their own or someone else's experience, you  
take it for what it was: a use case. That being said, I think there was  
some miscommunication.
Bill seems to be talking about no-op assignments

a = c;

while you've (probably correctly) hit on is:

a = foo(b);

which results in an assignment and happens everywhere.