🌐
crates.io
crates.io › crates › cyclic
cyclic - crates.io: Rust Package Registry
Browse All Crates · Log in with GitHub · Simple, complete, and dependency-free modular arithmetic · #modular · #arithmetic · #field · #cyclic · #group · about 6 years ago · 2018 edition · GPL-3.0 · 320 SLoC · 17 KiB · pkg:cargo/cyclic@0.1.1 · Run the following Cargo command in your project directory: cargo add cyclic ·
🌐
YouTube
youtube.com › minecraft mod whisperer
Minecraft Cyclic Crate - YouTube
#Shorts explaining how to build and use the Crate from the Minecraft mod Cyclic
Published   February 26, 2021
Views   1K
Discussions

My cyclic crates aren't stacking....

Could be nbt tag being different for some reason which results in that

More on reddit.com
🌐 r/allthemods
8
9
October 8, 2021
Does Cargo support cyclic dependencies?
I have 2 components that should live in the same crate, but because one of them is a proc_macro and proc_macro crates can only export proc_macros and nothing else (i.e. no types, no traits, no fns, etc), I have to create a rather unnatural architecture between the components. More on users.rust-lang.org
🌐 users.rust-lang.org
4
1
December 13, 2019
Allow crates to be published with cyclic dev-dependencies
The Rust package manager. Contribute to rust-lang/cargo development by creating an account on GitHub. More on github.com
🌐 github.com
51
July 1, 2017
cargo and how crates.io doesn’t like cyclic dev-dependencies
I really really think the cargo team should fix that issue, though. The teams are discussing it: https://github.com/rust-lang/crates-io-cargo-teams/issues/46 and https://github.com/rust-lang/crates.io/issues/1789 More on reddit.com
🌐 r/rust
10
11
August 23, 2019
🌐
GitHub
github.com › mcncm › cyclic-rs
GitHub - mcncm/cyclic-rs: A crate of generic cyclic groups and prime fields
A crate of generic cyclic groups and prime fields. Contribute to mcncm/cyclic-rs development by creating an account on GitHub.
Author   mcncm
🌐
Rust
docs.rs › cyclic
cyclic 0.1.1 - Docs.rs
Source code size: 52.12 kB This is the summed size of all the files inside the crates.io package for this release. Links · mcncm/cyclic-rs 1 1 0 · crates.io · Dependencies · cargo-husky ^1 dev · Versions · 0.1.1 · 0.1.0 · Owners · cyclic-0.1.1 doesn't have any documentation.
🌐
Rust
docs.rs › cyclic › latest › cyclic
cyclic - Rust
Using Cyclic is easy: the crate provides a macro, res!, that takes an unsigned integer and produces its residue class.
🌐
Rust Programming Language
users.rust-lang.org › help
Does Cargo support cyclic dependencies? - help - The Rust Programming Language Forum
December 13, 2019 - I have 2 components that should live in the same crate, but because one of them is a proc_macro and proc_macro crates can only export proc_macros and nothing else (i.e. no types, no traits, no fns, etc), I have to create a rather unnatural architecture between the components.
Find elsewhere
🌐
GitHub
github.com › rust-lang › cargo › issues › 4242
Allow crates to be published with cyclic dev-dependencies
July 1, 2017 - Currently I managed to work around it by specifying a version range but it would be nice if there was a way to publish a group of crates as a whole or to ignore the version check if a dev-dependency does not exist on crates.io (yet).
Author   rust-lang
🌐
Reddit
reddit.com › r/rust › cargo and how crates.io doesn’t like cyclic dev-dependencies
r/rust on Reddit: cargo and how crates.io doesn’t like cyclic dev-dependencies
August 23, 2019 - EDIT: A much more relevant issue that would definitely fix this along with other associated issues is https://github.com/rust-lang/cargo/issues/1169, this workspace is self-consistent, and after publishing it what is in crates.io will also be consistent, the only issue is that there is a period during the publish where there must be crates referring to unpublished versions.
🌐
Reddit
reddit.com › r/skyfactory › cyclic item cables + barrels?
r/SkyFactory on Reddit: Cyclic item cables + barrels?
July 19, 2019 -

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!

🌐
Fandom
skyfactory-4.fandom.com › wiki › Cyclic
Cyclic | Skyfactory 4 Wiki | Fandom
March 18, 2026 - All of the fluids added by cyclic can be picked up or placed with a bucket. They have limited usefulness on their own but are required for some crafting recipes. The following is a list of all of the new fluids added by cyclic, along with what happens when you jump into them.
🌐
Reddit
reddit.com › r/rust › library crate that uses an implementation crate in its benchmarks?
r/rust on Reddit: Library crate that uses an implementation crate in its benchmarks?
July 24, 2018 -

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?

🌐
crates.io
crates.io › crates › cyclic › reverse_dependencies
crates.io: Rust Package Registry
Browse All Crates · Log in with GitHub · Simple, complete, and dependency-free modular arithmetic · #modular · #cyclic · #arithmetic · #field · #group ·
🌐
Rust Programming Language
users.rust-lang.org › help
How to resolve cyclic dependency - help - The Rust Programming Language Forum
November 12, 2020 - But there's a dependency on the kernel library in the disk IO driver's crate as well, creating a dependency loop. As Cargo puts it: ```error: cyclic package dependency: package kernel v0.1.0 (C:\Users\ethin\source\kernel) depends on itself. Cycle: package kernel v0.1.0 (C:\Users\ethin\sour...
🌐
Rust
docs.rs › circular-buffer
circular_buffer - Rust
This crate implements a circular buffer, also known as cyclic buffer, circular queue or ring.
🌐
GitHub
github.com › rust-lang › cargo › issues › 9738
False positive cyclic dependencies when building for different targets · Issue #9738 · rust-lang/cargo
July 28, 2021 - If particular crate depends on crate A and crate B, such that if imported together, they would cause cyclic dependency, but crate B is only imported on specific target, for example wasm32, cargo will error out regardless of that target restriction.
Author   rust-lang
🌐
Reddit
reddit.com › r/rust › cyclic dependency on local crates
r/rust on Reddit: cyclic dependency on local crates
August 9, 2023 -

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?