On 2015/08/28 4:54, Jonathan Wakely wrote:
> On 27/08/15 21:48 +0200, Marc Glisse wrote:
>> On Thu, 27 Aug 2015, Jonathan Wakely wrote:
>>
>>> The std::cbegin function in can't call the
>>> std::begin function in unless it knows about it, so we need
>>> to declare the valarray overloads in .
>>
On 27/08/15 21:48 +0200, Marc Glisse wrote:
On Thu, 27 Aug 2015, Jonathan Wakely wrote:
The std::cbegin function in can't call the
std::begin function in unless it knows about it, so we need
to declare the valarray overloads in .
Hmm, do you remember why valarray has an ugly overload of std
On Thu, 27 Aug 2015, Jonathan Wakely wrote:
The std::cbegin function in can't call the
std::begin function in unless it knows about it, so we need
to declare the valarray overloads in .
Hmm, do you remember why valarray has an ugly overload of std::begin
instead of a nice member function be
The std::cbegin function in can't call the
std::begin function in unless it knows about it, so we need
to declare the valarray overloads in .
I considered adding a header with the
declarations, but I don't think that's worth it, so I'm just
declaring them directly in range_access.h
Tested pow
