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
Implement RFC 2523,
#[cfg(version(..))]
#71314Implement RFC 2523,
#[cfg(version(..))]
#71314Changes from all commits
90aa62a
96f27c7
a3ee283
8a77d1c
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.
Wow, do we need this? Or maybe we can try another crate
semver
?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 think this it's unlikely for anyone to run into this, but I wanted to explicitly document this problem. I have thought about using
semver
, however if I were to usesemver::Version
I'd need to make sure the version contains major, minor and patch versions, and if I were to usesemver::VersionReq
I'd need to check if the version literal doesn't contain things like>=1.0
,<1.5
,>1.2, <1.3
which the RFC only mentions as possible future work (However, as a first iteration, version(1.27.0) is simple and covers most use cases.
). Unless it's okay to implement this usingVersionReq
and adding support for>
,<
, etc. syntax I think it's simpler to just useversion_check
despite this bug which I believe is unlikely to affect anyone.