refactor use primordials in extensions/webgpu

[bartlomieju]

#11224

[satyarohith]

WebGPU flies are huge. I should've checked the line count of the files before I started the review. 😄

Nice work, Bartek. I couldn't find a single instance unaddressed.

LGTM.

[SimonRask]

Found some things in 01_webgpu.js:

• line 615
• line 1761
• line 1313

Found nothing in 02_idl_types.js

[satyarohith]

Thanks for taking a look, @SimonRask!

[ghost]

There were a few accesses on TypedArray/DataView objects that aren't using primordials here, e.g. directly accessing the .buffer property.

[bartlomieju]

There were a few accesses on TypedArray/DataView objects that aren't using primordials here, e.g. directly accessing the .buffer property.

@crimsoncodes0 I believe this is the same situation as with .length. Node doesn't really use primordials for such accesses.

[ghost]

There were a few accesses on TypedArray/DataView objects that aren't using primordials here, e.g. directly accessing the .buffer property.

@crimsoncodes0 I believe this is the same situation as with .length. Node doesn't really use primordials for such accesses.

String length are array length properties are safe to access, as that is the only way to access them. String have an immutable own property length, while arrays have a "magic" own property that has setting intercepted by the engine to cast the written value to an unsigned integer.

TupedArray properties are very different, in that they aren't nearly as safe, nor are they own properties. %TypedArray%.prototype.{buffer, byteLength, length} are all getters that exist on the %TypedArray% prototype, thus are able to be mutated by user code.

If it would be appreciated, I can make some PRs tommorow to use them across the JavaScript.

[bartlomieju]

@crimsoncodes0 thanks explanation. Please do open a PR.