Ron Buckton
Ron Buckton
@simllll: I cannot repro this. Is your project configured correctly? Top-level `await` is only supported in `--module nodenext` when the input file is an ES module, not a CommonJS module....
I should note, I tested against the following TS versions: - [email protected] - [email protected] - [email protected] - [email protected] All supported top-level `await` correctly when the source file will be treated...
It looks like our expectation (prior to `useDefineForClassFields`), was that parameter property initializers are assigned before instance initializers, as evidenced by the emit when `useDefineForClassFields` is `false`: ```js constructor(facade) {...
> ```ts > type Foo = { > true: something, > false: somethingElse > }[CompilerOptions['noUncheckedIndexAccess'] > ``` This specific example wouldn't work anyway since TS doesn't let you index a...
I tinkered with an example of a tail-recursive parser for `jest.each` [here](https://gist.github.com/rbuckton/cee71acbe68a3fac8b0b4babae58213a), though it can probably be drastically simplified.
Here's a much simpler version of Jest's `each`: ```ts type IDStart = | "a" | "b" | "c" | "d" | "e" | "f" | "g" | "h" | "i"...
There is no longer any order dependence. The behavior for inferring from an intersection of two tuple types now falls back to pre-existing behavior.
Also, I've added a test for Jest's `each` based on the example above.
@DanielRosenwasser: Are we comfortable taking this for 4.8 or would you rather wait?
@typescript-bot perf test @typescript-bot run dt @typescript-bot test this @typescript-bot user test this