Re: [boost] [optional] memory use for optional refs and ptrs

Subject: Re: [boost] [optional] memory use for optional refs and ptrs
From: Rutger ter Borg (rutger_at_[hidden])
Date: 2010-10-06 14:33:43

On 2010-10-06 19:19, Simonson, Lucanus J wrote:
>
> Just replicate the tuple interface but accpet and return optional<T>  for each element and store it as a bit_vector and a regular tuple internally.  Call it tuple_optional or tuptional or some such.  Such a library could be implemented, documented, tested and ready for review in about one week flat, but I have no interest in either writing it or using it.  I don't use optional either.
>

Sounds like a good starting point (or fusion vectors). Is there some 
kind of facility that is able to point to "padding space" in aligned 
structures? (perhaps a facility of the alignment stuff in boost)?

Cheers,

Rutger