RHS (right hand side) and LHS should be defined in the glossary

[AlexDaniel]

It is used several times but we never explain what it is. Googling it doesn't help.

Language/exceptions.pod6
159-A C<try>-block is a normal block and as such treats its last statement as the
160:return value of itself. We can therefore use it as a RHS.
161-

Language/terms.pod6
197-Constants are declared with C<constant>, followed by an
198:L<identifier|/language/syntax#Identifiers> and do not require a sigil. The RHS
199-is evaluated at compile time, therefore being possibly too early to make sense.
--
207-
208:Since constants RHS are evaluated at compile time, their usage within modules
209-could lead to unexpected behavior, please see the related

Language/syntax.pod6
549-When assigning to a C<%> sigiled variable on the LHS, the sigil and parenthesis
550:surrounding the RHS C<Pairs> are optional.
551-

Language/operators.pod6
1217-
1218:Both C<.count> and C<.arity> of the RHS will be maintained.
1219-

Type/Nil.pod6
99-If you are looking for a variable which transforms objects into type objects
100:when said variable appears on the RHS, you can type the container as C<Nil>.
101-

[AlexDaniel]

Well, if RHS is documented than LHS should be too.

[AlexDaniel]

At the same time, we no longer use this abbreviation in the docs: eb8f7f2

[JJ]

@AlexDaniel but it's good to have in the glossary anyway, right?

[AlexDaniel]

I think so, yeah.