Ed Page

Tracking Issue for _lockfile-publish-time_

4

### Summary Original issue: #5221 Implementation: #16265 Documentation: https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#lockfile-publish-time Disallow locking to registry packages newer than a specific time ### Unresolved Issues - [ ] How do we compensate for...

fix(publish): Move `.crate` out of final artifact location

3

When `target_dir == build_dir`, ensure `cargo publish` doesn't put intermediate artifacts in the final artifact location of `cargo package`. ### What does this PR try to resolve? In #15910, users...

Build Performance Chapter

5

### Summary Discussed on [Zulip](https://rust-lang.zulipchat.com/#narrow/channel/246057-t-cargo/topic/Build.20performance.20section.20in.20the.20Cargo.20book/with/537603929) Documentation: https://doc.rust-lang.org/nightly/cargo/guide/build-performance.html Implementation - [x] #15924 - [x] #15970 - [x] #15991 - [x] #16078 - [x] #16085 - [x] #16108 - [ ] Anti-virus...

### Summary Original issue: #15491 Implementation: #16265 Documentation: https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#pubtime Track the publication time for an Index Summary entry ### Unresolved Issues - [ ] How should we deal with Summary...

Tracking Issue for warnings (config build.warnings)

7

### Summary Original issue: #8424, #14258 Implementation: #14388 Documentation: https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#warnings Allows control over warnings via a new Cargo configuration option `build.warnings`. ### Unresolved Issues - [ ] What operations should...

Add non-lint `advice` messages controlled through a `[advice]` lint table

3

### Problem We have many situations where people would find additional information useful for new users at the cost of output blot. Potential cases - `cargo new`s `see more `Cargo.toml`...

### What it does Users may add the `version` field, thinking its relevant for git/path dependencies when it is instead adding a fallback registry source when published. While we can't...

Tracking issue: rust-lang/rust#136889

Conditional compilation makes it sound like `#[cfg(foo)]` will evaluate to `true` for `--cfg=foo="bar"` but it doesn't

1

From the [Reference](https://doc.rust-lang.org/reference/conditional-compilation.html#r-cfg.predicate.option): > A configuration option. The predicate is true if the option is set, and false if it is unset. And from the [Reference](https://doc.rust-lang.org/reference/conditional-compilation.html#r-cfg.option-spec) > *Configuration options* are...

Not quite sure whether to considering removing these to be a breaking change or not.