Re: [boost] [review][constrained_value] ReviewofConstrainedValueLibrary begins today

Subject: Re: [boost] [review][constrained_value] ReviewofConstrainedValueLibrary begins today
From: Robert Kawulak (robert.kawulak_at_[hidden])
Date: 2008-12-07 16:14:33

> From: Robert Kawulak
> > From: Chris
> >  Or add something like this:
> > class A {
> > 
> > A() { // fails
> > }
> > 
> > must_initialize<int> t;
> > };
> 
> The problem is that the fact whether the default value is 
> valid or not depends on the constraint used and this can't be 
> verified at compile-time in most cases.

This is even more tricky, because in some cases the error policy is able to
adjust the value to make it constraint conforming. So should the default
construction be disabled in such cases too or not?