Jim Blandy
Jim Blandy
... perhaps. Those two types both own an `Arc`, but Apple's [documentation for MtlCommandQueue](https://developer.apple.com/documentation/metal/mtlcommandqueue?language=objc) says: > Note > > Each command queue is thread-safe and allows you to encode commands...
In the WGSL front end, clarify error message for deeply nested statements. @ErichDonGubler I was going to push this as a suggestion to the PR but forgot to. Only take...
Acknowledging that nobody has made any claims about this being secure, and that the intended use is implicitly on non-hostile data: I believe that xor-ing together hashes is not secure....
Rust converts a `Pointer` to a `Pointer` where `T` implements `Trait` and `Pointer` is a type constructor like `&` or `Box`, *only* if `Pointer` is a thin pointer. The Nomicon...
If I do a compiletest test run under Emacs, Emacs sets the `TERM` environment variable to `"dumb"`, and then the test run panics: ``` running 2 tests test [compile-fail] asynchronous/async-fn-not-unpin.rs...
Two threads can deadlock as follows: - The first thread calls `Global::command_encoder_drop`, which locks `CommandBuffer::data` while calling `Device::untrack`, which then locks `Device::temp_suspected`. - The second thread calls `Queue::submit`, which locks...
The lock analyzers in the `wgpu_core::lock` module can be a bit simpler if they can assume that locks are acquired and released in a stack-like order: that a guard is...
Document some more safety expectations for - resource destruction methods - `CommandEncoder` methods - `Queue::submit` Document `Fence` creation a bit. Document the `Queue` trait a bit.
There are two bugs in `benchmark/cache-conflict/cache_conflict_benchmark.c`, one of which affects your results. Neither affects the conclusions drawn here: https://danluu.com/3c-conflict/ The bug that affects the results is that, although the intent...