shred
shred copied to clipboard
amethyst
Shared resource dispatcher
Hi, After experimenting a bith with Amethyst, I started wondering why the `System` trait is responsible for both `setup` and `run` (+`dispose`). I programmed my setup to fetch a resource,...
It seems to me that this feature may possibly be able to be written to have a safe API
There seems to be no need to have a lock around an option wrapping an `Arc` - since we have an (allocated) `Arc`, we can just use its raw pointer...
From what I've seen, there doesn't seem to be the ability to suspend `System`s? Basically, after exploring through `amethyst` and `specs`, I ended up concluding that `shred` would presumably be...
It would be useful to be able to inspect the plans shred comes up with, e.g. what systems execute in parallel when, and so on. It would also be useful...
In https://github.com/amethyst/shred/pull/228 I ran into the issue of the CI failing due to a dependency with a higher MSRV. If we had a lockfile to pin dependencies this would not...
``` warning: the following packages contain code that will be rejected by a future version of Rust: nom v5.1.2 ``` This is a minor issue since `cargo update` will update...
```rs #![warn( clippy::missing_safety_doc, clippy::multiple_unsafe_ops_per_block, clippy::undocumented_unsafe_blocks )] ```