Extended Type Design.

[Bill Baxter]

Andrei Alexandrescu (See Website For Email) wrote:
> Benji Smith wrote:

>> I reiterate: "const" and "readonly" are the way to go. (Methods which 
>> promise not to modify the values of their parameters should use 
>> "readonly" rather than "const" in their method signatures.)
> 
> This makes const gratuitously incompatible to C++'s const, and (worse) 
> also adds a keyword that's its equivalent. I don't think this can fly.

What about 'immutable' for 'really can't change'/'superconst', and const 
can stay as is?

--bb