This isn't really true. If you make opEquals const, then anything
opEquals calls must be const. Inevitably, you need to make a lot of
your object const, which then goes viral to things that object uses, etc.
On the other hand, I don't think opt-in const is that worthy a goal.
Things that are const, should be const.
-Steve
I totally agree - we need to take the plunge and roll const out through
phobos. If const (and immutable too for that matter) is broken in subtle
ways, then it needs to be fixed and then embraced.
--
Graham St Jack
