Undo WebGPU / GPUPipelineErrorReason and so on?

[jakebailey]

I've been snoozing this in my inbox for a while...

See gpuweb/types#192

#2076 introduced some GPU related stuff, which conflicts with other external types for this. That can be fine, but the types in this repo are incomplete and so people are stuck with either DOM or errors from other repos.

If WebGPU types here are not complete, can we omit them for the time being, and then address things more wholelistically later?

I'm mainly concerned because this partial declaration conflict seems to cause problems with repos like VS Code (which then block adoption of TS 6.0/7.0 once these libs are present).

Kagami Sascha Rosylight (@saschanaz) Kai Ninomiya (@kainino0x)

[saschanaz]

I'll see if I can focus back on webgpu.

[jakebailey]

It seems like based on #2376 and #2375 that the intent is to just finish it out?

Are we going to make the types match the linked repo above?

[saschanaz]

Are we going to make the types match the linked repo above?

I'm not sure? https://www.npmjs.com/package/@webgpu/types?activeTab=code shows a few things that never happened here like nominal types and new(): never, so I doubt it will be fully compatible.

[kainino0x]

I think once WebGPU types are officially upstream, that repository is going to have to switch anyway to just enhancing the official types. Should be doable, but I don't know offhand everything that will be in the diff and whether they'll all be addable using declaration merging.

There are some things in those types that are definitely not that critical, including both nominal types and new(): never, that can be dropped from the official types if you don't have the infrastructure to add them. And I think those can be added using declaration merging anyway.

[jakebailey]

Kagami Sascha Rosylight (@saschanaz) We're trying to finalize the 6.0 beta this week; do you know where the GPU types sit at this point?

(I think we can continue to patch the DOM libs for another 2 weeks tops, at which point we will cut RC)

[saschanaz]

A few more to add.

TypeScript-DOM-lib-generator/inputfiles/overridingTypes.jsonc

Lines 2872 to 2891 in d6afa4f

	// TODO: The following only exists to accept bcd@6.0.24 progressively,
	// and should be removed.
	"GPU": {
	"exposed": ""
	},
	"GPUAdapter": {
	"exposed": ""
	},
	"GPUCanvasContext": {
	"exposed": ""
	},
	"GPUCommandEncoder": {
	"exposed": ""
	},
	"GPUDevice": {
	"exposed": ""
	},
	"GPUQueue": {
	"exposed": ""
	},

[jakebailey]

There's also NavigatorGPU, it seems (just noticed the bcd@6.0.24 comment)

[kainino0x]

FWIW NavigatorGPU is an interface mixin and not visible to JS at all. Not sure if mixins normally appear in TS.

[saschanaz]

Mixins do, because it's used a lot in the IDL and TS prefers to use them rather than duplicating its members.