Skip to content
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

Rust 1.41.1 announcement #525

Merged
merged 3 commits into from Feb 27, 2020
Merged

Rust 1.41.1 announcement #525

merged 3 commits into from Feb 27, 2020

Conversation

Centril
Copy link
Contributor

@Centril Centril commented Feb 26, 2020

Written by myself and @pietroalbini.

r? @rust-lang/release @rust-lang/core @matthewjasper

posts/2020-02-27-Rust-1.41.1.md Outdated Show resolved Hide resolved
posts/2020-02-27-Rust-1.41.1.md Outdated Show resolved Hide resolved

Rust 1.41.1 addresses two critical regressions introduced in Rust 1.41.0:
a soundness hole related to static lifetimes, and a miscompilation causing segfaults.
These regressions are not affecting past releases of Rust,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, that's not really true -- the latest reproducer on rust-lang/rust#69225 goes back to 1.38, as long as we've been using LLVM 9.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Uh, woops.

Co-Authored-By: Kyle J Strand <BatmanAoD@users.noreply.github.com>

If you have a previous version of Rust installed via rustup, getting Rust 1.41.1 is as easy as:

```console
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This isn't feedback, more of a question. Is console now the preferred marker for CLI instructions? Is there any meaningful difference?

posts/2020-02-27-Rust-1.41.1.md Outdated Show resolved Hide resolved
posts/2020-02-27-Rust-1.41.1.md Show resolved Hide resolved
```

In Rust 1.41.1, this issue was fixed [by the same PR as the one above][pr_69145].
Compiling the program now produces the following error:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've been out of the loop lately, but I can't find any crater runs for this. Maybe it's worth mentioning whether any code was doing this on crates.io?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we have one.

Co-Authored-By: Tyler Mandry <tmandry@gmail.com>
@Mark-Simulacrum Mark-Simulacrum merged commit c93c619 into rust-lang:master Feb 27, 2020
steveklabnik pushed a commit that referenced this pull request Mar 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants