9114283707
* Texture state full is dead code * temp * temp2 - next is lifetime only * temp3 - all trackers in place * temp4 - continue muddling along * temp5 - doodle doodle * temp6 - continuous progress is continuous * temp7 - pro-gress * temp8 - Add refcounts to trackers * temp9 - Soundness, generics, refcounts, and epochs * temp10 - Compiling?!1?!1?!1 * temp11 - Add bind group state optimization * temp12 - Safety and adding size setting * temp13 - unsafe * temp14 - Abstract all the state transitions * temp15 - It verks! kinda... * temp16 - it more verks! * temp17 - debugging and unit tests * temp18 - fixing unfixed things * temp19 - hmmm * temp20 - curious about line deltas * temp21 - working texture trackers * temp22 - write merge/update/barrier for buffers * temp23 - cleanup and buffers * temp24 - clippy cleanup * temp25 - Add inline markers on buffer functions * temp26 - Fix buffer trackers * temp27 - fixed texture insert to handle both sides * temp28 - document tracker and usages * temp29 - document track/mod.rs * temp30 - convert STORAGE_WRITE to STORAGE_READ_WRITE * temp31 - Add some debug asserts to make sure we can't insert invalid states * temp32 - clippy is opinionated sometimes * temp33 - renaming and documentation * temp34 - logging |
||
|---|---|---|
| .. | ||
| examples | ||
| src | ||
| Cargo.toml | ||
| README.md | ||
wgpu-hal is an explicit low-level GPU abstraction powering wgpu-core. It's a spiritual successor to gfx-hal, but with reduced scope, and oriented towards WebGPU implementation goals.
It has no overhead for validation or tracking, and the API translation overhead is kept to the bare minimum by the design of WebGPU. This API can be used for resource-demanding applications and engines.
Usage notes
All of the API is unsafe. Documenting the exact safety requirements for the
state and function arguments is desired, but will likely be incomplete while the library is in early development.
The returned errors are only for cases that the user can't anticipate, such as running out-of-memory, or losing the device. For the counter-example, there is no error for mapping a buffer that's not mappable. As the buffer creator, the user should already know if they can map it.
The API accept iterators in order to avoid forcing the user to store data in particular containers. The implementation doesn't guarantee that any of the iterators are drained, unless stated otherwise by the function documentation. For this reason, we recommend that iterators don't do any mutating work.
Debugging
Most of the information in https://github.com/gfx-rs/wgpu/wiki/Debugging-wgpu-Applications still applies to this API, with an exception of API tracing/replay functionality, which is only available in wgpu-core.