mirror of
https://github.com/cargo-bins/cargo-binstall.git
synced 2025-04-22 05:28:42 +00:00
Rm unused BinstallError::VersionWarning
Signed-off-by: Jiahao XU <Jiahao_XU@outlook.com>
This commit is contained in:
parent
c87941211c
commit
aecc474f29
1 changed files with 0 additions and 17 deletions
|
@ -166,22 +166,6 @@ pub enum BinstallError {
|
|||
v: semver::Version,
|
||||
},
|
||||
|
||||
/// Warning: The resolved version may not be what was meant.
|
||||
///
|
||||
/// This occurs when using the `--version` option with a bare version, like `--version 1.2.3`.
|
||||
/// That is parsed as the semver requirement `^1.2.3`, but the user may have expected that to
|
||||
/// be an exact version (which should be specified with `--version '=1.2.3'`.
|
||||
///
|
||||
/// - Code: `binstall::version::warning`
|
||||
/// - Exit: none (runtime warning only)
|
||||
#[error("version semantic mismatch: {ver} <> {req}")]
|
||||
#[diagnostic(
|
||||
severity(warning),
|
||||
code(binstall::version::warning),
|
||||
help("You specified `--version {req}` but the package resolved that to '{ver}'.\nUse `--version '={req}'` if you want an exact match.")
|
||||
)]
|
||||
VersionWarning { ver: String, req: String },
|
||||
|
||||
/// This occurs when you specified `--version` while also using
|
||||
/// form `$crate_name@$ver` tp specify version requirements.
|
||||
#[error("duplicate version requirements")]
|
||||
|
@ -217,7 +201,6 @@ impl BinstallError {
|
|||
VersionReq { .. } => 81,
|
||||
VersionMismatch { .. } => 82,
|
||||
VersionUnavailable { .. } => 83,
|
||||
VersionWarning { .. } => unimplemented!("BUG: warnings do not terminate"),
|
||||
DuplicateVersionReq => 84,
|
||||
};
|
||||
|
||||
|
|
Loading…
Add table
Reference in a new issue