00:13
<TabAtkins>
Yeah, reduce() def needs the presence check rather than undefinedness.
01:33
<Michael Ficarra>
shu: FYI there's another 2 iterator helper topics added to the May agenda
01:33
<Michael Ficarra>
they're some minor inconsistencies that I discovered while working on the tests
01:34
<Michael Ficarra>
the slides should be self-explanatory
01:45
<shu>
do they really need 30 minutes each
01:47
<Michael Ficarra>
hopefully not
01:51
<Michael Ficarra>
does anyone remember a discussion about whether const [] = { [Symbol.iterator]() { return {}; } }; (a malformed iterator that never gets iterated) should throw?
01:51
<Michael Ficarra>
I vaguely remember Justin Ridgewell being involved I think
01:53
<Michael Ficarra>
bakkot found it! https://github.com/tc39/ecma262/pull/1288#issuecomment-424457388
01:53
<Justin Ridgewell>
We discussed whether a malformed iterator would close the underlying
01:55
<Michael Ficarra>
notes: https://github.com/tc39/notes/blob/main/meetings/2018-09/sept-25.md#normative-use-getmethod-instead-of-getv-to-get-iterator-next
02:25
<bakkot>
had not encountered this particular downside of floats
02:26
<bakkot>
though it's of course an instance of the same problem as all the other things we've been discussing lately
02:26
<bakkot>
(this example is from https://speleotrove.com/decimal/decifaq.html about why a Decimal type is warranted)
12:29
<littledan>
I'm curious what you're trying to do that made you run into this--was it just researching decimal, or do you have a specific application? I got the feeling that the committee as a whole wasn't totally convinced that decimal was actually a general-purpose, useful thing, as opposed to something very specialized.
14:50
<bakkot>
finally got around to reading the FAQ linked during the discussion, which has this example
14:50
<bakkot>
I didn't actually run into it in real life
15:29
<littledan>
ah OK. Yeah I really enjoyed the FAQ.