https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77760
--- Comment #8 from Alexandre Oliva <aoliva at gcc dot gnu.org> --- https://gcc.gnu.org/pipermail/gcc-patches/2023-February/612198.html has a simple-minded implementation, that should make it clear what I mean by scratch: get() pays no regard to the incoming bits in tm, it initializes them with a zeroed-out state. Now, I realize that do_get, if called by a derived class with an uninitialized tm, might do weird things, because it would take some of those bits as state. Is this something of concern? As in, how internal and reserved for the implementation is the intermediate state of tm between get and do_get?
