-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cargo test
fails in package named "core"
#180
Comments
cargo test
fails in when package is named "core"cargo test
fails in package named "core"
If you know a way to fix this, feel free to make a PR. Otherwise, maybe just don't call your crate the same as one from the standard library? |
@JelteF we can fix this by referring |
3 tasks
tyranron
added a commit
that referenced
this issue
Dec 26, 2023
## Synopsis See #180 (comment) for details. At the moment, compilation fails in a local crate `core` is present in workspace or some another crate is renamed as `core`. ## Solution Use `::derive_more::core` instead of `::core` in macro expansions. Co-authored-by: Jelte Fennema-Nio <github-tech@jeltef.nl>
liveseed
added a commit
to liveseed/derive_more
that referenced
this issue
Aug 20, 2024
## Synopsis See JelteF/derive_more#180 (comment) for details. At the moment, compilation fails in a local crate `core` is present in workspace or some another crate is renamed as `core`. ## Solution Use `::derive_more::core` instead of `::core` in macro expansions. Co-authored-by: Jelte Fennema-Nio <github-tech@jeltef.nl>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the following project,
Cargo.toml
:core/Cargo.toml
:core/src/lib.rs
:...
cargo check
works fine, butcargo test
gives:cargo test
works fine if package is not namedcore
.The text was updated successfully, but these errors were encountered: