bors[bot] b01a4bb169 [rs] Merge #82 ...

82: Return Queue separately r=grovesNL a=kvark

What problem is this PR trying to solve? We want `Device` to be freely accessible from multiple threads/objects and internally synchronized. `Arc<Device>` seems like a natural choice of such a sharable object, especially since all except one methods are `&self`.

That one method is `get_queue()`, and it returns a temporary object `Queue<'a>`. If we turn it into `&self`, we'd end up with multiple instances of `Queue` created at any time, which contradicts the initial design (of this Rust wrapper). If it stays `&mut` and the user wraps the device into `Arc`, they'll never be able to submit any work...

So this PR solves this by moving the `Queue` completely outside of the device.

Co-authored-by: Dzmitry Malyshau <dmalyshau@mozilla.com>

2019-09-10 13:27:14 +00:00

wgpu

[rs] Return Queue separately

2019-09-10 09:26:18 -04:00

.gitignore

[rs] Mipmapping example

2019-06-16 21:15:15 -07:00

.travis.yml

[rs] Update wgpu-native to the commit that has no backend features.

2019-08-29 22:04:43 -04:00

Description

No description provided

137 MiB

Languages

Rust 79.9%

WGSL 16.2%

HLSL 2%

GLSL 1.7%

JavaScript 0.2%