Re: [boost] Deterimining interest in: Optional Polymorphic Value object with Small Object optimization

Corrado Zoccolo wrote:

Hi I've uploaded a new version of the library in the vault: * http://tinyurl.com/2og6st* It now provides also a new class (poly<T>) that maintains the never-empty guarantee. poly<T> and optional_poly<T> share a large part of their implementation, so I think it is sound to have both in the same library.

Hmm, it seems inherent that poly is DefaultConstructible(Nullable), IMHO. Why not introduce `nonnullable`? nonnullable< poly<T> > nonnullable< boost::shared_ptr<T> > BTW, poly<void> can't be "any"? Regards, -- Shunsuke Sogame