Jake Bailey
Jake Bailey
Actually, why isn't this being stuck into the iterable d.ts file?
For 6.0, we're going to make the DOM types `reference` ES6/ES2015 (and promote DOM.Iterable to just being DOM), so we could probably just wait a bit and this will all...
Yes, since that's what we do in the main libs, but I suppose that would be pretty noisy.
In any case, I think we should shelve this temporarily, at least until I put together a PR for this repo to introduce a 6.0 variant that makes the iterable/es2015...
> In any case, I think we should shelve this temporarily, at least until I put together a PR for this repo to introduce a 6.0 variant that makes the...
I think it did, because these are generated files and so are not formatted, I guess. I don't think this is worth the churn. Probably we should just update the...
Yes, this effectively a type assertion in disguise. It's not good to have this kind of signature. An explicit assertion is much preferred.
I understand the risks but I don't think this is a good idea. (If we were to have something like this, it'd at least have to be `T extends ......
> My case for it: `querySelector` and `querySelectorAll` have it. I have no idea why these have it, I doubt we would choose to do so if the same decision...
querySelector has overloads that have nice return types, but then they end with: ```ts querySelector(selectors: string): E | null; querySelectorAll(selectors: string): NodeListOf; ``` I'm not sure if that's because it's...