Wesley Wigham
Wesley Wigham
Iirc, the `react` PRs were waiting for react 18 to ship, because react 17's exports were partially broken.
(So yeah, PRs welcomed - the existing checked ones in the op should serve as decent guidance)
@Andarist is currently working on adjusting the TS semantics a smidge to match this, and I'm open to the change, since it's pretty reasonable from a compatibility perspective.
We used to have machinery to preserve required augmentations by adding `///
@jakebailey thoughts?
The augmentation is what makes the type instantiation valid to make - otherwise the type is unconstructable. (Basically, the `Apply` type doesn't know how to make a `ReadonlyTuple` out of...
Hm, I think this one might be because `Promise` isn't defined in the lib `transpileDeclaration` uses, and `async` functions always have to `Promise`-wrap their returns (so it's not like the...
@typescript-bot perf test this faster
@typescript-bot perf test this faster I still need to sprinkle around setting the `calculatedFlags` for nodes during the full typecheck pass (likely just by setting all of them when the...
Much better, no more check regressions, only emit ones, and those aughta get fixed with proper application of `.calculatedFlags` during the checker walk (though it's admittedly pretty odd that only...