Jack Works

> @stiff the problem is that users don't use them when it's not syntactic. `await` is easy to overuse, when `await.all` would be much more correct and performant. Actually IMHO...

Playground v2: https://www.typescriptlang.org/play/index.html?ts=4.0.0-pr-39224-4&ssl=1&ssc=1&pln=5&pc=2#code/IYZwngdgxgBAZgV2gFwJYHsIwLbFRACgEoYBvAKBipmAHc9kA6YAGxZgAZLqpMRkYAbQAeAXRgBeGvVRNWLQQAUATumyoQAU0bLNIdCwBumggCYAzOaKjuVYY2ToAosIAOmTRDSti5AL5AA Playground v3: [Playground Link](https://www.staging-typescript.org/play?ts=4.0.0-pr-39224-4#code/IYZwngdgxgBAZgV2gFwJYHsIwB4AoCUMA3gFAzkzADuwqyAdMADZMwAMZF1tDATsFACmMANoAFXugC2qEIPq9BIdEwBug3AEZ8AXU7ludRiwDKg5MiaCAJqL0BfIA)

I think this is a must for this proposal. #67 might be a solution for this

If so, how do we mark a higher-order iterator?

I think this is a little strange that allow the developer to custom the standard library. It's should be predefined at the platform level or language spec level.

But polyfills and shims are implementing something that in the spec. If you define your own std lib, this is likely going to make your own dialect of JavaScript. Why...

So just extends this proposal, make it like this syntax? https://developers.google.com/web/fundamentals/primers/modules#layered-apis > The element loads the virtual-scroller API either from the browser’s built-in set of layered APIs (std:virtual-scroller) or from...

> Another option is just to have > BigInt.min, BigInt.max But this means we should add `Math.min` to `Number.min` to keep the consistency.

> I think the committee would probably push back against adding a new global. They would probably rather add methods to BigInt. > I will raise the possibility of using...

But we need to throw syntax error or early errors before we run the code. It will be super strange to throw a syntax error at the time of your...