> Therefore to justify > boost::optional as a key in an associative container, as > opposed to its > direct type, I believe one has to justify a situation where > the "non-actual" > value is really being used as a key.
Let say I have mapping of state to action. Now I want to support the case where current state is undefined. So I am using optional<state> as a key. Does this example fit for the situation? Gennadiy. _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
