Nicolas Silva a697e4352c Keep the value in its storage after destroy (#4678) ... * Keep the value in its storage after destroy in #4657 the destroy implementation was made to remove the value from the storage and leave an error variant in its place. Unfortunately this causes some issues with the tracking code which expects the ID to be unregistered after the value has been fully destroyed, even if the latter is not in storage anymore. To work around that, this commit adds a `Destroyed` variant in storage which keeps the value so that the tracking behavior is preserved while still making sure that most accesses to the destroyed resource lead to validation errors. ... Except for submitted command buffers that need to be consumed right away. These are replaced with `Element::Error` like before this commit. Co-authored-by: Teodor Tanasoaia <28601907+teoxoy@users.noreply.github.com>		2023-11-14 14:23:23 +00:00
..
src	[wgpu-test] Fix typo in error message.	2023-11-13 14:23:32 -08:00
tests	Keep the value in its storage after destroy (#4678)	2023-11-14 14:23:23 +00:00
Cargo.toml	Extra Profiling Scopes (#4610)	2023-10-30 03:58:32 +00:00