Re: [boost] Iterator Range and operator==

Subject: Re: [boost] Iterator Range and operator==
From: Olaf van der Spek (ml_at_[hidden])
Date: 2012-04-21 05:47:33

On Sat, Apr 21, 2012 at 11:33 AM, Dave Abrahams <dave_at_[hidden]> wrote:
>> It is current behaviour. But is it expected behaviour?
>
> Yes.

Based on what? Knowledge of this issue?

> Until the language gives us a way to distinguish string literals
> from other arbitrary arrays of char, it's the best we can do.  The
> alternative is to have generic code suddenly stop working when T==char.

What about requiring the use of as_array or as_literal in all cases?

-- 
Olaf