Shu-yu Guo

Oo that parking sign is a great and compelling example.

> I wish we didn't have this constructor lookup gross-ness Das Leben ist kein Wunschkonzert :((

A related data point: ecma262 currently is trying to fix its definition of arithmetic so all actual operations are done on the reals. Waldemar lists good reasons to do this...

Recapping some off-thread discussion: it seems to come down to whether specs should mandate rounding be cumulative on intermediate results, or only observable on the final result if the intermediate...

@iainireland is right, this is a problem with "notify one". It probably also bears to note that these were designed to implement condition variables and mutexes and so forth, and...

> The intention is for it to be for implementation-contributed tests that don’t yet meet the bar for being full test262 tests. That way, implementations are less likely to duplicate...

Currently all of the tests in staging are related to Temporal. As for why the majority of them fail... perhaps @ptomato can chime in? Those are still supposed to be...

> Sure, hence why I'd like to see separation similar to what already exists with [test/intl402/](https://github.com/tc39/test262/tree/main/test/intl402). Baseline Temporal is ISO8601 + UTC with offsets only. Hm, probably a good idea...

> is staging/intl/ or something? or staging/262 and staging/402? Yeah all of those seem fine to me. If the main suite distinguishes 402 vs 262, staging should too.

I don't have too much of a language design opinion here, but having iterator helpers that can _mostly_ reuse async generator machinery except for return/throw might be annoying for implementation...