Add #buffer-uploads about mapping in modern graphics APIs and copyDataToBuffer example.
#680
Conversation
…taToBuffer` example.
There was a problem hiding this comment.
I agree this material could be useful. It's not obvious to me that it needs to be in the specification though, perhaps a tutorial or some kind of "best practices" document would make more sense?
I also don't think we want to put this in while the heated discussions about uploads are still on-going.
The group mostly agrees that, given the uploading is one of the frequently needed tasks, it makes sense for the API to provide a simple mechanism for it, even if there is a more complex approach that could be more efficient. And once we decide what this mechanism is (writeToXxx, inlineUploadBuffer, or something else), this paragraph would have to be scraped anyway.
|
I think this should stay unlanded until the writeToX discussion, so removed for-meeting. Does that make sense? |
|
Closing now that #708 is landed. |
I keep wanting to refer back to this recommendation for easy buffer uploads, so I think it makes sense to propose some non-normative spec text about it.
This applies to the state of the spec today, and may or may not change based on ongoing work on buffer upload entrypoints.
Preview | Diff