And then, again, in most instances for me, this was also a no.
You can cast away const-ness.
Sometimes you want something that was set to be const to not be const,
so you would make it modifiable.
But in my sense, you're mixing up two characteristics.
Why did you make it const in the first place?
So you're really saying, I'll make that thing mostly const.
I don't want pi to all of a sudden change.
I don't wanna say, gee, It's going to be pi, but
there may be some time I wanna tweak that, it's just not how I'm gonna think.
So again, most of these other kinds of casts,
you basically be throwing out of your repertoire.
Safe casting is okay, the old style casting,
while available in many compilers is deprecated.
Deprecated means, don't use it,
the compiler writer is at liberty of actually denying its use.
And then there are some special cases where
class hierarchies involve dynamic casting, where
when you're doing some very fancy object oriented programming this may be required.
But again I'm not a fan, so I would say safe casting, yes.