Re: [boost] [optional] Making optional more debugger friendly

Joe Gottman wrote:

If I want to see the result of an optional, I often write code that looks like the following:

optional<int> opt; /// Time passes... if (opt) { const int &i = *opt;

Then I can just watch i. I do the same thing with iterators, especially into sets and maps.

Joe Gottman

That's a technique I use, but it's intrusive. I use boost::optional like a value type. I'd like it to be as transparent to the debugger as the type it wraps. My coworkers have also expressed this issue when I started using boost::optional in our code. Is there anybody out there besides me that would find this useful? If not, I'm happy to drop it. I can always implement it locally for our own use. Jeff