Variable Prefix Miscount

[librasteve]

Problem or new feature

This section https://docs.raku.org/language/variables#Variable_declarators_and_scope says...

There are also two prefixes that resemble declarators but act on predefined variables:

Prefix	Effect
temp	Restores a variable's value at the end of scope
let	Restores a variable's value at the end of scope if the block exits unsuccessfully
constant	Declares that a container value is not going to change during its lifetime

Suggestions

I count 3

;-)

[coke]

good catch, thanks.

[coke]

66a7177

[raiph]

That seems like the wrong fix.

Only temp and let act on a predefined variable. (constant declares one.)

Perhaps the constant row should have been in the previous table (and the "two" was correct)?

It's perhaps outside the, er, scope of this issue, but the text of that row is wrong:

Declares that a container value is not going to change during its lifetime.

I would strawman propose:

Declares a name that's immutably bound at compile time to whatever its initialized with.

[librasteve]

I like @raiph proposals on constant

[librasteve]

Since this is the only place I have (ever) seen let and temp, I am curious about their typical use, so this could use a bit more explanation.

Maybe something like:

my $a = 1;

{
    temp $a = 2;
    say $a;   #2  
}

say $a;  #1  

and this

my $b = 1;

{
    let $b = 2;
    say $b;   #2  
}

say $b;  2#

So another concern is that let and temp are called 'Prefix's BUT they are not used as a prefix to the declaration.

Elsewhere I would say that e.g. my is a prefix for my class A {} or e.g. our is a prefix for our sub(). So maybe better to call let and temp "Modifiers".

And perhaps some admonishment to using the form let my $a =1 since that is accepted by the compiler, but is contrary (aiui) to the intent.