Waldemar Horwat

Towards the end of 13.2 the `CoverCallExpressionAndAsyncArrowHead` is refined to [ParenthesizedExpression](https://tc39.es/ecma262/#prod-ParenthesizedExpression)[Yield, Await] : ( [Expression](https://tc39.es/ecma262/#prod-Expression)[+In, ?Yield, ?Await] ) I see what you mean about the missing "must cover" rule in...

The current spec doesn't accept decimal points. It also doesn't accept exponential notation; I'm not sure whether that's intentional or not.

That's not a sound interpretation. The text only mentions the characters 0-9, A-Z, and a-z. Trying to construe it as anything that can be produced by toString leads to all...

Many folks spell hexadecimal numbers using upper case, so I'd prefer accepting either case for bases >10. We can make an exception for mixed case "NaN" and "Infinity" in high...

michaelficarra wrote: > Here's my ideal implementation that wraps up all of my preferences: > > ```js > const once = fn => { > let completed = false, errored...

I'm not sure I'm happy with the combination of `*` always returning exact results and BigDecimal having arbitrary precision. It's too easy for the precision to run away from you...

It's a fairly broad question. I think that IEEE decimal (without distinguishing cohorts) has more predictable behavior and applicability — you can do math, trigonometric functions, etc., and they behave...

The [General Decimal Arithmetic Specification](https://speleotrove.com/decimal/decarith.pdf) has both kinds of remainder. They call the IEEE 754 version *remainder-near*.

I didn't realize that `if` differs from `{}` in setting the prior completion value to undefined instead of empty. But we can modify the second example to, say: ``` a...

What's the question about _integrity_ of lexical scoping?