Valentin Milea

To be clear: the `HashAdapter` wraps the hash, but is a distinct template parameter on the container. So if the user changes the `Hash`, the avalanching policy continues to be...

Related issues: https://github.com/KhronosGroup/Vulkan-ValidationLayers/issues/2918, https://github.com/KhronosGroup/Vulkan-ValidationLayers/issues/6216.

I've created a [live sample](https://vmilea.github.io/webgpu_buffer_upload_test/) to illustrate the issue with mapping large buffers. The code is [public](https://github.com/vmilea/webgpu_buffer_upload_test) and works on Chrome or Firefox Nightly. You can adjust the amount of...

> That's definitely the intent and Chromium should implement that optimization at some point, we just didn't get around to it yet. That makes the problem more tractable. Thanks for...

As a tangent, why does `getMappedRange()` exist? I consider it too rigid for tracking written ranges. Does it provide any other benefits compared to `mapAsync(mode, offset, size)` returning `Promise` directly?

Thanks for the feedback. > If you have some kind of streaming write, and so you know the offset but not the size, you can getMappedRange() in blocks until you...

Given the mentioned constraints, and the expected browser [optimizations](https://issues.chromium.org/issues/360704483), I think it's fine to close this issue. > written ranges can be inferred from getMappedRange(offset, size) as mentioned in the...