Subject: bug#63410: 30.0.50; [FR] Optionally allow defcustom to check type for standard value

From: Drew Adams <[email-masked]>
Date: Wed, 10 May 2023 13:36:49 +0000

> Similar to `setopt' introduced in 29, which warns when a variable gets
> assigned a value with an incorrect type, I hope `defcustom' can
> (optionally) check that the standard value of a customizable variable is
> correct.  This would help external as well as internal package authors
> to catch errors on the types.

Not sure I understand.  Doesn't it do that already,
showing "mismatch" next to the default value if it
doesn't match the type definition?