On Tue, 28 Aug 2018 at 19:00, Walter Bright via Digitalmars-d <digitalmars-d@puremagic.com> wrote: > > There's been some talk of adding a "mutable" qualifier for fields, which would > stop the transitivity of const at that point. But it has problems, such as > what > happens with opaque types. The compiler can no longer check them, and hence > will > have to assume they contain mutable members.
Exactly. And you arrive at C++. 'c-const' and 'turtles-const' probably need to be specified differently from the top, not broken along the way with the likes of mutable.
