Skip to content
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

Using moongraph and apecs both in a crate causes compile error. #8

Open
navneetankur opened this issue Jun 6, 2024 · 4 comments
Open

Comments

@navneetankur
Copy link
Contributor

navneetankur commented Jun 6, 2024

   |
14 | pub use apecs_derive::Edges;
   |         ------------------- previous import of the macro `Edges` here
...
18 |     end, err, graph, ok, Edges, Graph, GraphError, Move, NodeResults, TypeKey, TypeMap, View,
   |                          ^^^^^ `Edges` reimported here
   |
   = note: `Edges` must be defined only once in the macro namespace of this module
help: you can use `as` to change the binding name of the import
   |
18 |     end, err, graph, ok, Edges as OtherEdges, Graph, GraphError, Move, NodeResults, TypeKey, TypeMap, View,
   |                          ~~~~~~~~~~~~~~~~~~~

For more information about this error, try `rustc --explain E0252`.

@navneetankur navneetankur changed the title Using moongraph and apecs both in a crate causes comile error. Using moongraph and apecs both in a crate causes compile error. Jun 6, 2024
@schell
Copy link
Owner

schell commented Jun 6, 2024

Mmmm, I see. 🤔 .

@schell
Copy link
Owner

schell commented Jun 6, 2024

Each of the two libraries have a derive feature flag that you could try turning off by doing (for example):

apecs = { version = "0.8.1", default-features = false }

And that might fix it.

@navneetankur
Copy link
Contributor Author

apecs = { version = "0.8.1" ,default-features = false }
moongraph = { version = "0.4" } 

Didn't work. Still same error.
Although with NoDefault reexported I no longer need to use moongraph anyway. But someday I or someone Might. :)

@schell
Copy link
Owner

schell commented Jun 9, 2024

I'll keep this open then, and get to it when I can :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants