Sitelet https://github.com/gpuweb/gpuweb/pull/468
Skip to content

Change setVertexBuffers to setVertexBuffer - #468

Merged
kainino0x merged 1 commit into
gpuweb:masterfrom
austinEng:set-vertex-buffer
Oct 9, 2019
Merged

kainino0x merged 1 commit into
gpuweb:masterfrom
austinEng:set-vertex-buffer

Conversation

@austinEng

@austinEng austinEng commented Oct 9, 2019 •

Copy link
Copy Markdown
Contributor

We determined in #421 that setVertexBuffer is both more ergonomic and more
performant for JavaScript bindings.


Preview | Diff

We determined that setVertexBuffer is both more ergonomic and more
performant for JavaScript bindings.
@kainino0x

Copy link
Copy Markdown
Contributor

We already decided in the meeting, so merging this. (Force merging because the failure is unrelated and due to the bikeshed update)

@kainino0x
kainino0x merged commit 3ea1405 into gpuweb:master Oct 9, 2019
@kainino0x kainino0x mentioned this pull request Nov 4, 2019
13 tasks done
ben-clayton pushed a commit to ben-clayton/gpuweb that referenced this pull request Sep 6, 2022
* Refactor dataBytesForCopy to be safer, mostly update usages, fix duplicate offset+

* fix bytesPerSlice computation in layout.ts

* fix handling of bytesPerRow/rowsPerImage in test

* fix the destination origin/offset in texture checking?

* Skip formats for which the checking implementation does not work

* TODO encodeExtent3D

* Rename files+tests and add descriptions

* address comments

* helpers for dataBytesForCopy

* oops fix
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants