Feature or Enhancement?

• (x) New feature
• ( ) Enhancement of existing feature

Description

Currently, for using pseudo-variables, the following syntax sugar exists:

• @= name [ s"val" ] => push s"val" write_cache s"name" d1
• @= name d1 => write_cache s"name" d1
• @name => read_cache s"name"

If these values are to be used in locking scripts that do not also write them, it will be necessary to check the number of values held by these variables. This requires use of OP_READ_CACHE_SIZE, which has an alias: rcz s"name". It will be nice to have syntax sugar for this use as follows:

• @#name => rcz s"name"

While it is less clear than using the full op names for newcomers/casual observers, I have found that I very much like all the previous syntax sugar I have added, as well as the comptime features, so I am confident this will be very nice when using these features.

Additional context

I've already written the code. I just need to make some compilation test vectors.

Also, the way to safely use cache values specified by an unlocking script is to use check_template_verify to ensure they have been committed to by a signature.