No. constexpr is great upcoming keyword that means something. What
does immutable help? There will be always book authors who think that
software developer is stupid moron and language engine should know
better how to write software.
People reading your code look also at casts. If you don't know what
you are doing then you will be badly beaten by review and sent back to
your Actionscript or PHP team.
I forgot to ask what y'all would prefer ideally (either/or/both) and if
there is any talk about an "immutable" keyword as a possibility in a
future standard or if the committee feels that const fits the bill
adequately and entirely.
It is unneeded. If i need only immutable objects then i make classes
that do not have any methods to mutate the instances. Plain and
simple.
In C++ one will always be able to cast anything to anything if he
knows what he does. He can still reinterpret my immutable object into
pile of chars and hack there but then it is his fault if something
fails.