[05:58:27] <wm-bb>	 <u99of9> I'm having trouble at Z21437. When I run the same input string in Try this function, I get the correct answer (expand the result to see exponent=1). But in the Test failure details it says an exponent of -511 is returned.
[08:30:27] <wm-bb>	 <Al> There was a leading space 🤷‍♂️ (re @u99of9: I'm having trouble at Z21437. When I run the same input string in Try this function, I get the correct answer (expand the result...)
[11:21:35] <wm-bb>	 <u99of9> Grr, all my testing involved copying the string from the html display, and I didn't notice that the line break before it could have been due to a space. Thanks for saving me further headaches. I'm also glad that it was a simple error, because I was getting worried that there was a deep problem with float64s in general. (re @Al: There was a leading space 🤷‍♂️)
[11:25:20] <wm-bb>	 <Al> Not unlike my double-space in the search function… There is a usability issue here that clearly needs to be addressed! (re @u99of9: Grr, all my testing involved copying the string from the html display, and I didn't notice that the line break before it could h...)
[11:32:59] <wm-bb>	 <Al> I’ll add it to “The list” (eventually). (re @Al: Not unlike my double-space in the search function… There is a usability issue here that clearly needs to be addressed!)
[22:54:13] <wm-bb>	 <u99of9> "An integer _after_ stating how many units before the timestamp could the moment be" Are those in units of the precision? https://www.wikifunctions.org/wiki/Wikifunctions:Time_in_Wikidata
[22:55:38] <wm-bb>	 <u99of9> This is a really nice piece of work to prepare us well to represent times. Compatibility with Wikidata is so crucial.
[22:57:10] <wm-bb>	 <Al> I think it would have to mean that. But it doesn’t follow of necessity, no. (re @u99of9: "An integer after stating how many units before the timestamp could the moment be" Are those in units of the precision? https://...)