Gregory's Server
@RealGene @Mara I don't see how super let would complicate parsing. Rust parser has to do some weird things, but this is not one of them.
The problem with make is that it's not a reserved keyword, so we'd need to introduce a new keyword in an edition, use ugly k# in previous ones and also disallow people from using it for names. A lot of noticeable disadvantages.
Besides IMO it's nice that super is reading as a modifier, it should help teaching "this is like let but with a small twist..."
@wffl @Mara
IANAL but: super is already in use as a keyword/adjective to identify a module parent.
So now the parser must distinguish between 'super let' and 'super::let'.
The behavior described for super let doesn't yet exist anyway, so a new release would be required regardless.
So add 'make' as a super let, or 'durable' or 'perpetual' as a let modifier when you add the functionality…
You want a modifier to at least hint at what it's going to do. Super is kind of vague.
@wffl @Mara
IANAL but: super is already in use as a keyword/adjective to identify a module parent.
So now the parser must distinguish between 'super let' and 'super::let'.
The behavior described for super let doesn't yet exist anyway, so a new release would be required regardless.
So add 'make' as a super let, or 'durable' or 'perpetual' as a let modifier when you add the functionality…