Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Add a
compile_error!()
when central crate features clash #110base: master
Are you sure you want to change the base?
Add a
compile_error!()
when central crate features clash #110Changes from all commits
06ed053
5115eef
7d29fb9
ab47652
adbc618
cd40d4f
f110a2e
b650660
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You name these
features
but they're implicit from the optional dependencies, and "renamed" (but without"dep:..."
) tov4l2
andlibv4l
. I think we should specify exactly what the user is enabling, or expected ot enable:There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not do what you've done in the second patch (but the other way around):
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would also prefer this, but I found that doing so breaks one of the features.
On the other hand, it doesn't occur in
api.rs
since we're not already re-exporting one of its modules. If you find a way to do it, though, please let me know!There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would match the choice in
api.rs
to preferv4l2
code in the case that both features are contemporarily enabled, but it is less of an issue now that the comment has been removed.Either way, this seems better to me: