bug#40693: 28.0.50; json-encode-alist changes alist

[Drew Adams]

> @defspec quote object
>  This special form returns @var{object}, without evaluating it.
> +The returned value is a constant, and should not be modified.
>  @end defspec

Not true.

The returned value _can be_ a constant, e.g., if the
code is byte-compiled, and depending on the kind of
object that's returned.

'foo returns the symbol foo.  Depending on the
context, you can certainly modify the properties of
that symbol - its `symbol-value', `symbol-function',
and `symbol-plist'.

This kind of wholesale change risks making things
less clear instead of more clear.

See also Eli's message about the purpose of the
manual, and the need to handle this overall message
(about the byte-compiler sometimes causing a return
value to become a constant) in a single place.

The message should be about not _depending_ on a
quoted value returning a new object (e.g. new list
structure).  The message should not be that `quote'
never returns a new object.

> +If a subexpression of a backquote construct has
> +no substitutions or splices, it acts like
> +@code{quote} in that it yields a constant that
> +should not be modified.

A constant is not something that _should not_ be
modified.  It's something that _cannot_ be modified.

And something that should not be modified is not
a constant.  For a constant, there's zero reason
to tell users not to modify it or tell them that
they should not modify it - they _cannot_.