-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Release notes for 1.8 #32810
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
Release notes for 1.8 #32810
Conversation
(rust_highfive has picked a reviewer for you, use r? to override) |
instead return widened integers. [RFC 1415]. | ||
* [`btree_set::{IntoIter, Iter, Range}` are covariant][1.8cv]. | ||
* [Atomics are not volatile][1.8a]. | ||
* [All types is `sync::mpsc` implement `fmt::Debug`][1.8mp]. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is
* [Tuple and unit enum variants from other crates are in the type | ||
namespace][1.8tn]. | ||
* [MSVC builds of Rust on Windows emit `.lib` files for the `staticlib` | ||
library type instead of `.a` files][1.8st]. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This actually affects all Rust on Windows, both gnu and msvc. The change that is specific to msvc is that import libraries for dylibs were renamed from foo.lib
to foo.dll.lib
, and it is only specific to msvc because gnu currently doesn't emit import libraries.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the clarifications.
Thanks for putting these together @brson ! |
May also want to mention that there are now a bunch of new nightly releases of rustc and cargo for these hosts: 3 arm linux triples, aarch64 linux and {net,free}bsd. And libstd binaries for i686-musl (did this reach prod yet?) and mips(el)-musl. However, I don't know if any of those will have a stable/beta release next week. Perhaps @alexcrichton can confirm that? |
Right of course! I guess maybe it's a little soon to announce rustup, but we've got a whole mess of new target standard libraries built just yet. Unfortunately the compilers @japaric mentions are only available on nightly (soon to be beta), but we've got new targets like:
|
Addressed feedback. I mentioned the new binary targets and snuck in a link to the urlo post explaining how to use them w/ multirust. |
@steveklabnik The new targets are probably a highlight. |
b9a27f4
to
64c3a27
Compare
* [On Windows `rustc` emits `.lib` files for the `staticlib` library | ||
type instead of `.a` files][1.8st]. Additionally, for the MSVC | ||
toolchain, `rustc` emits import libraries named `foo.dll.lib` | ||
instead of `foo.dll`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
instead of foo.lib
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
haha
Will check this out soon. |
across platforms was making it difficult to implement `std` | ||
correctly. Those that need these definitions should use the `libc` | ||
crate. [RFC 1415]. | ||
* The Unix-specific `MetadataExt` traits, including |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems like there's a missing comma in this sentence, or a disagreement between "exposes" and its subject.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch
Looks good here! Agree with your summary of important stuff. Once this is r+'d, I'll work on the announcement post. |
r=me with the fixes mentioned here |
@bors r+ p=1 |
📌 Commit 94a387e has been approved by |
[1.8h]: https://github.com/rust-lang/rust/pull/31460 | ||
[1.8l]: https://github.com/rust-lang/rust/pull/31668 | ||
[1.8m]: https://github.com/rust-lang/rust/pull/31020 | ||
[1.8m]: https://github.com/rust-lang/rust/pull/31534 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
duplicate link label, causing wrong target for one of the links
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PR was merged without fixing this, cc @brson
Release notes for 1.8 cc @steveklabnik to me the highlights are compound assignment overloading, 32-bit MSVC builds being ready for use, and the cargo improvements. [Rendered](https://github.com/brson/rust/blob/relnotes/RELEASES.md).
|
||
* [`cargo init` creates a new Cargo project in the current | ||
directory][1.8ci]. It is otherwise like `cargo new`. | ||
* [Cargo has configuration keys for `-v` and |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If I am not mistaken another new subcommand in this release is cargo metadata
.
the link under cargo "The environment variables CARGO_TARGET_ROOT, RUSTC, and RUSTDOC take precedence over the build.target-dir, build.rustc, and build.rustdoc configuration values." does not seem to link to where it's supposed to link to |
cc @steveklabnik to me the highlights are compound assignment overloading, 32-bit MSVC builds being ready for use, and the cargo improvements.
Rendered.