25b16d5cc8
* First attempt of exposing create_surface_from_canvas for webgl * Test Fix Compile For WebGL Offscreen Canvas * Only specify web-sys feature version in wgpu-core, so that patch version is taken from workspace * Reuse already existing fn create_surface_from_canvas * Remove unnecessary unsafe * Remove unsafe prefix also from top-level create_surface_from_canvas * Add create_surface_from_offscreen_canvas() for webgl * Cargo fmt * Store webgl2_context instead of canvas, which works also for OffscreenCanvas * Copy skybox example for OffscreenCanvas example * Use offscreen_canvas instead in newly created example * Update skypbox_offscreen readme.md * Allow enabling OffscreenCanvas in examples via http://localhost:8000/?offscreen_canvas=true * Fix cargo fmt * [fix warning] Only import FromStr for wasm32 * [fix warning] Exclude offscreen_canvas_setup from non-wasm32 * [fix warning] Add ImageBitmap feature as well so that all related methods can be used * Fix cargo fmt * Fix emscripten build * Remove `webgl` feature from wgpu-core as webgl is the only wasm32 backend Co-authored-by: Zicklag <zicklag@katharostech.com> |
||
|---|---|---|
| .. | ||
| examples | ||
| src | ||
| Cargo.toml | ||
| LICENSE.APACHE | ||
| LICENSE.MIT | ||
| 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.