Re: [boost] [contract] concept error messages

Subject: Re: [boost] [contract] concept error messages
From: Matt Calabrese (rivorus_at_[hidden])
Date: 2012-10-07 17:12:40

On Sun, Oct 7, 2012 at 4:28 PM, Matt Calabrese <rivorus_at_[hidden]> wrote:

>  The problem is, if you have two concepts with the same requirements other
> than something like Derived on an associated type, and you had two
> overloads (one for each of the aforementioned concepts), calls to the
> overloads would be ambiguous even with requires in the case where you are
> dealing with an iterator_category style hierarchy for the associated type.
> This should be true unless N3351-style concepts either decide to support
> explicit concept maps instead of the Derived/iterator category hack, or
> alternatively, if the Derived concept is altered to have special meaning
> when doing matching.
>

Ah, nm, I see how this works now in N3351 -- the explicit requirement for
the less-refined concept.

-- 
-Matt Calabrese