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

Features are not mutually exclusive #1

Open
pinkforest opened this issue Jul 8, 2024 · 0 comments
Open

Features are not mutually exclusive #1

pinkforest opened this issue Jul 8, 2024 · 0 comments

Comments

@pinkforest
Copy link

pinkforest commented Jul 8, 2024

If two crates uses this (though this may be much rarer with bevy pipeline?)

The features don't get bifurcated meaning conflicting output size and looking at the code it picks the first if-match.

You might want to use cfg() instead if it's mutually exclusive and top level binary must choose it unless you can get it through API - features are supposed to only add code and not "switch" stuff

Not sure if this is an issue in bevy context but 🤷‍♀️

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

1 participant