My cyclic crates aren't stacking....
Could be nbt tag being different for some reason which results in that
More on reddit.comDoes Cargo support cyclic dependencies?
Allow crates to be published with cyclic dev-dependencies
cargo and how crates.io doesn’t like cyclic dev-dependencies
Videos
any suggestions?
Hi!
I may have found either a bug, or something that I do not understand. I have a tree farm, which works perfectly, and I collect everything into a single chest. Now, the chest in question has a Cyclic Item extractor attached to it, and a bunch of cables which run into different barrels.
However, for some reason it doesn't want to put items into the barrels, but if I attach a chest to the cable system, it immediatly puts the items there.
Is there any special thing required to store items into the barrels, or is this a bug?
Forgot to mention, I am using Sky factory 4.
Thank you for your help!
I have a library crate that provides a number of traits. I have another crate that depends on it, and provides implementations of those traits. Is it possible to use the implementation crate in benchmarks/tests inside the library crate?
I've tried to go about this in a couple of ways, with no success.
The quickest failure was to name the implementation crate as an optional dependency of the library crate, using a feature. This failed with a "cyclic package dependency".
The next was specifying the implementation crate as a dev-dependency of the library crate. No cyclic dependency, but when I try to use the implementations from the crate, they are not recognized as implementors of the traits in the library crate (In the library test module, I use super::Thing, but compilation fails and suggests that I use library_crate::Thing instead). Presumably because the library crate gets compiled first, as a dependency of the implementation, and then the implementation gets compiled, and then the library gets compiled again for the tests, and by that point it doesn't recognize the traits as being the same.
Is this possible?
I want to add a preprocessor to my Compiler and want it to be mentally decoupled from the actual compiler since should have nothing to with it.
My current package structure looks like this: there is the main-crate which is a library+binary crate consisting of the compiler and the preprocessor lib-crate which is needed by the main.rs
package - preprocessor -- src/lib.rs (uses ../src/error.rs) -- Cargo.toml -src -- main.rs (uses preprocessor) -- lib.rs -- error.rs (contained inside lib) -Cargo.toml
I want to be able to access my error data structure from my preprocessor lib though.
However when preprocessor/Cargo.toml has dependencies: package = {path = ".."} and package has preprocessor as an dependency then its a cyclical reference and it complains.
Do i have to split up the library+binary crate into two separate things like so:
package - preprocessor -- [dependency] compiler_lib - compiler_lib -- Cargo.toml - src/main.rs -- main.rs - Cargo.toml [dependencies] compiler_lib, preprocessor
would this be the idiomatic way to do things or can I keep my bin+lib structure the way it is?
I just decided to go explore and I'm surrounded by nothing but swamp for like 2.5k blocks... Is there any large portable storage I can use to move all my items out of the swamp?
Ae2 or refined storage should be good. Bit expensive but worth it. Melanism boxes are great for moving machines, just be careful with stuff like that and ae
For simple relocating I would go for bags of holding, if you don't have a huge number of container or a complicated setup.