Updated RELEASES.md for 1.29.0#53030
Conversation
|
Should this mention clippy-preview? |
RELEASES.md
Outdated
| ----- | ||
| - [Cargo can silently fix some bad lockfiles ][cargo/5831] You can use | ||
| `--locked` to disable this behaviour. | ||
| - [`cargo-install` will now ignore the target triple specified in a project |
There was a problem hiding this comment.
Per this comment it seems like this was reverted again.
RELEASES.md
Outdated
| directory's `.cargo/config`.][cargo/5606] | ||
| - [`cargo-install` will now allow you to cross compile an install | ||
| using `--target`][cargo/5614] | ||
| - [Added the `cargo-fix` to automatically move project code from 2015 edition |
There was a problem hiding this comment.
You might add a noun somewhere like "subcommand" or "tool", like:
Added the
cargo fixsubcommand
RELEASES.md
Outdated
|
|
||
| Misc | ||
| ---- | ||
| - [`rustdoc` now has the `--cap-lints` which allows you to set what level of |
There was a problem hiding this comment.
rustdocnow has the--cap-lints
Remove the "the".
which allows you to set what level of lint will cause and compilation failure.
The purpose of cap-lints is to make all lints not exceeding the specified level. For instance, if we pass --cap-lints warn, then all lints with level deny or forbid will be demoted to warn.
Perhaps just express this flag being "equivalent to that in rustc".
RELEASES.md
Outdated
| ---- | ||
| - [`rustdoc` now has the `--cap-lints` which allows you to set what level of | ||
| lint will cause and compilation failure.][52354] | ||
| - [`rustc` and `rustdoc` will now have the exit code of one if compilation |
There was a problem hiding this comment.
I suggest writing "1" instead of "one" here...
RELEASES.md
Outdated
| ------------------- | ||
| - [`str::{slice_unchecked, slice_unchecked_mut}` are now deprecated.][51807] | ||
| Use `str::get_unchecked(begin..end)` instead. | ||
| - [`std::env::home_dir` is now deprecated for it's unintuitive behaviour.][51656] |
|
Looks good to me, looks like there's a few other things we should add to it though (see comments above). |
|
|
|
|
||
| Compiler | ||
| -------- | ||
| - [Bumped minimum LLVM version to 5.0.][51899] |
There was a problem hiding this comment.
Sorry if this is naive to ask -- but is this ever actually visible to users? Isn't LLVM vendored either way?
There was a problem hiding this comment.
It's relevant to distros, so worth noting here I think.
There was a problem hiding this comment.
Again, this is entirely me being uninformed, but if you have time do you mind explaining to me why it is relevant to distros? (If you don't have time or don't care to explain this I completely understand)
There was a problem hiding this comment.
Since we've removed code from the LLVM shims that was needed for 4.9 (or whatever the previous version was, maybe 3.9) compatibility, distros that package that previous LLVM might need to do more work now. However, I believe that someone did a loose survey and we believe that most if not all distros are on 5.0+ already.
There was a problem hiding this comment.
Isn't it vendored either way though?
There was a problem hiding this comment.
You can build with your own external LLVM too, and distros usually do.
|
|
||
| Libraries | ||
| --------- | ||
| - [`Once::call_once` now no longer requires `Once` to be `'static`.][52239] |
There was a problem hiding this comment.
I'm not sure what this means. Are you referring to the closure being passed to call_once? Once is either 'static or not, it's not a generic type -- the user has no control over whether that type is 'static
There was a problem hiding this comment.
Not the closure, previously call_once takes a &'static self.
There was a problem hiding this comment.
What do you think about rephrasing this as "Once::call_once now takes &self instead of &'static self"?
|
Let's get this landed, if necessary we can iterate further. @bors r+ rollup |
|
📌 Commit b4924bf has been approved by |
Updated RELEASES.md for 1.29.0 [Rendered](https://github.com/Aaronepower/rust/blob/master/RELEASES.md) r? @Mark-Simulacrum cc @rust-lang/release
Rollup of 17 pull requests Successful merges: - #53030 (Updated RELEASES.md for 1.29.0) - #53104 (expand the documentation on the `Unpin` trait) - #53213 (Stabilize IP associated constants) - #53296 (When closure with no arguments was expected, suggest wrapping) - #53329 (Replace usages of ptr::offset with ptr::{add,sub}.) - #53363 (add individual docs to `core::num::NonZero*`) - #53370 (Stabilize macro_vis_matcher) - #53393 (Mark libserialize functions as inline) - #53405 (restore the page title after escaping out of a search) - #53452 (Change target triple used to check for lldb in build-manifest) - #53462 (Document Box::into_raw returns non-null ptr) - #53465 (Remove LinkMeta struct) - #53492 (update lld submodule to include RISCV patch) - #53496 (Fix typos found by codespell.) - #53521 (syntax: Optimize some literal parsing) - #53540 (Moved issue-53157.rs into src/test/ui/consts/const-eval/) - #53551 (Avoid some Place clones.) Failed merges: r? @ghost
Rendered
r? @Mark-Simulacrum
cc @rust-lang/release