Avoid using pkg* unified patterns in documentation, as they might introduce ambiguities. #3032
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Master to develop
Master to develop
Master to develop
There are libraries with a common prefix that might introduce ambiguities now or later, e.g. zlib and zlib-ng. Prefer using `pkg/*` over `pkg*` which is more explicit.
|
|
oxygene
changed the title
memsharded
approved these changes
Feb 28, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Avoid using
pkg*unified patterns in documentation, as they might introduce ambiguities.There are packages with common prefix out there (or might be introduced in future). Using
pkg*e.g. for options could match more than intended by the user, e.g. when a new librarypkg-ngis added to the project later.Prefer using
pkg/*instead.See discussion at conan-io/conan#13233 (comment)