Re: macro BOOST_HAS_CONCEPTS not work + namespace for concepts

From: Gero Peterhoff (g.peterhoff_at_[hidden])
Date: 2023-02-19 23:45:55

Am 20.02.23 um 00:07 schrieb Matt Borland:
> 
> On Sun, Feb 19, 2023 at 10:16, Gero Peterhoff via Boost <boost_at_[hidden] <mailto:boost_at_[hidden]>> wrote:
>> Am 19.02.23 um 17:48 schrieb John Maddock via Boost:
>> > On 19/02/2023 13:48, Gero Peterhoff via Boost wrote:
>> >> Hi John,
>> >> Sure, you would have to fix that first to make it work at all and mark it as deprecated in the same breath.
>> > Given that it's only used in two places in Boost, and only supported by an ancient experimental compiler which was never released, I'll probably just remove it from the docs. I'm not sure it had any business being there in the first place.
>> >>
>> Then do this quickly so that nobody gets the idea of actually using it.
>> >> But what about my proposal for a concept-namespace?
>> >
>> > I have no opinion ;)
>> >
>> > Matt's suggestion for a new Concept library that extends on <concepts> is a good one, but someone else will have to write it ;)
>> >
>> I'm happy to help, but I need *detailed* information about how this is planned, eg
>> 1) Will the previous implementations of boost::concept and boost::concept_check be removed?
>> 2) Can I use the boost::concepts namespace?
>> 3) Could I write something like <boost/concepts.hpp> (see attachment)?
>> > John.
>>
>> thx
>> Gero
>>
> 
> Gero,
> 
> Are there specific concepts you are looking for?
> 
In principle not. However, all type-traits that can be represented as a concept should also be available as a concept. And there are quite a few missing from <type_traits>/<boost/type_traits>.
I mean simple things first. It gets exciting then, for example, with range-library(s).
> Matt
thx
Gero