jugglinmike

I'll give it a shot!

I'm currently writing tests for `signDisplay: "negative"`

Here's a progress update: feature | status -------------------------------|------- formatRange | [under review](https://github.com/tc39/test262/pull/3283) Grouping Enum | [under review](https://github.com/tc39/test262/pull/3301) New Rounding/Precision Options | [under review](https://github.com/tc39/test262/pull/3334) Interpret Strings as Decimals | [under review](https://github.com/tc39/test262/pull/3307)...

I'll take "Interpret Strings as Decimals", next

I'll take "New Rounding/Precision Options", now

@rwaldron's thoughts match my own. While stewarding Test262, he and I have set a pretty high bar for abstractions, both due to their many drawbacks and due to the aspects...

This issue was created following the initial implementation of the tests in gh-3048. The discussion in that pull request has additional information about the kinds of tests we need to...

It looks like GitHub.com restricts the accounts which can be assigned to a given issue. The information in [the tracking issue for the Temporal tests](https://github.com/tc39/test262/issues/3002) will have to do.

I was also hoping to avoid iteration in the callbacks because of the verbosity that you've highlighted. If we want distinctive failure messages, then it will be even more noisy...

> @jugglinmike — Thanks for your thoughts! I wanted to think it all through as deliberately as I could, since collaborating with folks you don't know well can lead to...