Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow max_bind_groups to be missing, for now #356

Merged
merged 1 commit into from
Oct 24, 2019
Merged

Conversation

kvark
Copy link
Member

@kvark kvark commented Oct 24, 2019

Fixes #355

@kvark
Copy link
Member Author

kvark commented Oct 24, 2019

We'll revert this once gfx-rs backends are exposing the limit properly.
I think it's safe to merge now.
bors r+

bors bot added a commit that referenced this pull request Oct 24, 2019
356: Allow max_bind_groups to be missing, for now r=kvark a=kvark

Fixes  #355

Co-authored-by: Dzmitry Malyshau <kvarkus@gmail.com>
@bors
Copy link
Contributor

bors bot commented Oct 24, 2019

Build succeeded

@bors bors bot merged commit f3a0dd9 into master Oct 24, 2019
@kvark kvark deleted the kvark-max-bind-groups branch October 24, 2019 17:23
parasyte added a commit to parasyte/wgpu that referenced this pull request Nov 2, 2019
bors bot added a commit that referenced this pull request Nov 2, 2019
372: Followup for #356 - fix incorrect check r=kvark a=parasyte

@kvark This fixes the fix created in #356 

The original patch is checking the _requested descriptor limits_, but the backend limits are what needs to be checked for this edge case.

Co-authored-by: Jay Oster <jay@kodewerx.org>
kvark pushed a commit to kvark/wgpu that referenced this pull request Jun 3, 2021
356: Add generic ranges to buffer mapping api and make it safe. r=kvark a=lachlansneff

[Rendered](https://charted.space/notes/wgpu-rs/wgpu/struct.Buffer.html)

The safety issues with the current api (being able to unmap while still holding a slice to mapped data) are fixed by having `get_mapped_range` and `get_mapped_range_mut` return `BufferView` and `BufferViewMut`, which notify the buffer that those ranges are no longer being used when they're dropped. `Buffer.unmap` asserts that the list of mapped ranges is empty, therefore it is safe.

Co-authored-by: Lachlan Sneff <lachlan.sneff@gmail.com>
Patryk27 pushed a commit to Patryk27/wgpu that referenced this pull request Nov 23, 2022
…'static str (gfx-rs#356)

* Changed front::glsl::error::ErrorKind::Semantic to use Cow

* cargo fmt

* appeasing clippy

* Update src/front/glsl/functions.rs

Co-authored-by: monocodus[bot] <49363530+monocodus[bot]@users.noreply.github.com>

* Fixed more clippy errors

Co-authored-by: Dzmitry Malyshau <kvark@fastmail.com>
Co-authored-by: monocodus[bot] <49363530+monocodus[bot]@users.noreply.github.com>
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.

Panic with DX12 VirtualGpu
1 participant