mirror of https://github.com/rust-lang/cargo
feat(lints): `lints` feature skeleton
This commit is contained in:
parent
a6c0d43787
commit
4d09a6a745
|
@ -483,6 +483,9 @@ features! {
|
|||
|
||||
// Allow specifying rustflags directly in a profile
|
||||
(stable, workspace_inheritance, "1.64", "reference/unstable.html#workspace-inheritance"),
|
||||
|
||||
// Allow specifying rustflags directly in a profile
|
||||
(unstable, lints, "", "reference/unstable.html#lints"),
|
||||
}
|
||||
|
||||
pub struct Feature {
|
||||
|
|
|
@ -93,6 +93,7 @@ Each new feature described below should explain how to use it.
|
|||
* [codegen-backend](#codegen-backend) --- Select the codegen backend used by rustc.
|
||||
* [per-package-target](#per-package-target) --- Sets the `--target` to use for each individual package.
|
||||
* [artifact dependencies](#artifact-dependencies) --- Allow build artifacts to be included into other build artifacts and build them for different targets.
|
||||
* [`[lints]`](#lints) --- Configure lint levels for various linter tools
|
||||
* Information and metadata
|
||||
* [Build-plan](#build-plan) --- Emits JSON information on which commands will be run.
|
||||
* [unit-graph](#unit-graph) --- Emits JSON for Cargo's internal graph structure.
|
||||
|
@ -1391,6 +1392,10 @@ Valid operations are the following:
|
|||
* When the unstable feature is on, fetching/cloning a git repository is always a shallow fetch. This roughly equals to `git fetch --depth 1` everywhere.
|
||||
* Even with the presence of `Cargo.lock` or specifying a commit `{ rev = "…" }`, gitoxide is still smart enough to shallow fetch without unshallowing the existing repository.
|
||||
|
||||
### `[lints]`
|
||||
|
||||
* Tracking Issue: [#12115](https://github.com/rust-lang/cargo/issues/12115)
|
||||
|
||||
## Stabilized and removed features
|
||||
|
||||
### Compile progress
|
||||
|
|
Loading…
Reference in New Issue