zopsicle
zopsicle
I suppose defining the COM interfaces as [extern types](https://github.com/rust-lang/rust/issues/43467) rather than structs would solve the problem of out of bounds access.
Seems to have been fixed in the documentation for PhysX 5: https://nvidia-omniverse.github.io/PhysX/physx/5.1.0/docs/Simulation.html#completion-tasks. Thanks!
Was this fixed in https://github.com/KhronosGroup/glslang/pull/3066?
This crate no longer depends on the nix crate (since 68c8bf54cacf25951ff0996b0e3ae650f5d53e62), so I think this issue can be closed.
Simply don’t put task `A` on the queue until `B` and `C` have completed. You can do this by having `B` and `C` share an atomic counter. Once either task...
The PR was merged, can this issue be closed?
For signalfd to be useful, pthread_sigmask with an argument of SIG_BLOCK should also be exposed. This is necessary, for instance, to handle SIGTERM using signalfd.
Perhaps it can be a separate method `Closure::{new,once}_with_this` that only accepts Rust functions that take at least one argument.
The reason for this is that in some implementations of C++, the size of a base object can be smaller than its alignment. If base objects in C++ are translated...