Re: [boost] GSoC: Enforcing Code Feature Requirements

Subject: Re: [boost] GSoC: Enforcing Code Feature Requirements
From: vicente.botet (vicente.botet_at_[hidden])
Date: 2010-03-31 07:50:08

----- Original Message ----- 
From: "Joel Falcou" <joel.falcou_at_[hidden]>
To: <boost_at_[hidden]>
Sent: Wednesday, March 31, 2010 8:55 AM
Subject: Re: [boost] GSoC: Enforcing Code Feature Requirements

> 
> vicente.botet wrote:
>> Hi,
>> 
>> I have recently reread the article "Enforcing Code Feature Requirements in C++" by Scott Meyers <http://www.artima.com/cppsource/codefeaturesP.html>
>> 
>> I have posted some ideas that could improve the design (<http://www.artima.com/forums/flat.jsp?forum=226&thread=238798&start=0#372622>)
>> 
>> I wanted to know if this could be a good subject for GSoC, if the approach I purpose to solve some issues is acceptable and if there is some students interested. 
>> 
>> Of course any comments are welcome.
>> 
> 
> I like the idea of playign with this, but: isn't this somethign Concept 
> and Concept-based SFINAE should handle ?

Sure concepts can help. In my proposition I use traits class to set all the features, but a trait by features is also possible to emulate concepts.

IIUC SFINAE needs to add a parameter to the function. The main goal of my approach is to don't need such a parameter. 

Joel, maybe you can elaborate how the Concept/SFINAE approach manages with this problem.

Best,
Vicente