Back

@Crell @sji

I easily see folks using them by default as a way to prevent redefining variables.

Then they'll want to add type declarations, another RFC.

People who hate `$` will also start to favor them so the next RFC will be to allow input arguments as constants.

Then add in 'shadowing', another RFC.

It will create a mix of inconsistent syntax and knock-on effects.

They're a form of state, with no way for child classes to use or override them.

@zimzat @Crell Thanks for helping me think about it. That foresight will probably be real.

I myself tend to use relatively short-lived variables that don't be re-assigned, and TBH never experience problems with local variables having state. And as Crell says, private class constants are enough for actually constant values.

Though I think that write-once variables can be a way to reduce cognitive load, I'm still not convinced that it would be worth the added complexity of the language.