Avoiding code duplication and retaining const correctness
First you have it the wrong way around.

You should not use the mutating version to supply data to the non-mutating function:

const int&amp; MyClass::operator[](int index)const {
    return const_cast&lt;int&amp;&gt;(const_cast&lt;MyClass&amp;&gt;(*this)[index]);
}


What happens if operator[] is modified and does mutate slightly the internal state? By casting away the constness you have opened up your class to undefined behavior. You should NEVER cast away constness. If you must you can use const_cast to add constness, but removing it is so dangerous that this should be looked at as breaking code.

If you had written it the other way around:

int&amp; MyClass::operator[](int index) {
    return const_cast&lt;int&amp;&gt;(const_cast&lt;MyClass const&amp;&gt;(*this)[index]);
}


This is better. Because if you change the operator[] so that it actually mutates the class it will generate a compiler error and thus prevent you from accidentally getting undefined behavior. 

But personally I prefer to add another helper method and thus remove all athe casting:

private:
// NOTE: This is not a perfect solution for all situations.
//       But it works for 99% of situations and keeps the code clean
//       For the remaining situations switch back to use const cast
//       **BUT** always add never remove constness from an object.
// Never make public as it is const and gives away an internal reference.
// Only use via the public API
int&amp; get(int index) const
{
    return stuff[index];
}

public:
// Keep the API simple/clean and DRY
// move all the work to private methods.
int&amp;       operator[](int index)       { return get(index);}
int const&amp; operator[](int index) const { return get(index);}


Answer to comment below:

I would not use it for const/non-const iterators

const_iterator begin() const {return const_iterator(&lt;X&gt;);}
iterator       begin()       {return iterator(&lt;X&gt;);}