00:51
<Michael Ficarra>
we could really use a better font on the spec
00:52
<Michael Ficarra>
I'd prefer something that dots/slashes zero, but also we could select something with better general legibility
00:53
<Michael Ficarra>
also, it would be better to use a web font so everyone has the same experience instead of using a font list with Windows-exclusive fonts at the highest priority (looking at you, Brian!)
01:27
<Michael Ficarra>
  1. Let t be ((h * msPerHour + m * msPerMinute) + s * msPerSecond) + milli, performing the arithmetic according to IEEE 754-2019 rules (that is, as if using the ECMAScript operators * and +).

uh, isn't that just how math on Numbers works in the spec? why do we say it like this?

07:44
<bakkot>
we don't generally do nontrivial math on Numbers
12:51
<jmdyck>
If multiplication and division count as nontrivial, I count 7 other places: Day, TimeFromYear, HourFromTime, MinFromTime, SecFromTime, MakeDate, Date.prototype.getTimezoneOffset
12:55
<jmdyck>
Not sure how much bother it would be to shift those to mathematical ops.
12:58
<jmdyck>
side question: is there any interest in having those <emu-eqn> ops converted into proper abstract operations?
15:12
<Michael Ficarra>
jmdyck: Yes, I would love that!
15:13
<Michael Ficarra>
I was just thinking about that yesterday
15:13
<Michael Ficarra>
we don't generally do nontrivial math on Numbers
that's because we typically desire precise semantics, not float semantics, like here
15:14
<Michael Ficarra>
I don't think that has anything to do with an editorial choice