Subject: bug#23926: defcustom with STANDARD=<non-pure-expression> gives confusing results

From: Eli Zaretskii <[email-masked]>
Date: Sat, 09 Jul 2016 10:13:00 +0300

> From: Noam Postavsky <[email-masked]>
> Date: Fri, 8 Jul 2016 23:11:02 -0400
> 
> A trivial example:
> 
> (defcustom time (current-time-string)
>   "the time"
>   :type 'string)
> 
> Then try to M-x customize-options RET time RET, it will show with
> state "CHANGED outside Customize." Similarly, doing <f1> v time RET
> shows the "original value" as the current time, not the actual value
> when `time' was defined.

Why is this a bug?  Seems to be expected behavior to me.