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.

Sign up for GitHub

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

1.25 announcement #237

Merged
merged 4 commits into from
Mar 29, 2018
Merged

1.25 announcement #237

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
f78a6d3
first part of 1.25 announcement
steveklabnik Mar 22, 2018
b89915d
more
steveklabnik Mar 23, 2018
158a14a
Fixup nits
Mark-Simulacrum Mar 29, 2018
3976db7
Reword to not call pulldown-cmark a "rendering"
Mark-Simulacrum Mar 29, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Fixup nits
  • Loading branch information
@Mark-Simulacrum
Mark-Simulacrum committed Mar 29, 2018
commit 158a14afd25d3c4a849809dfc1bd07220aa017f5
26 changes: 13 additions & 13 deletions _posts/2018-03-29-Rust-1.25.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,19 +62,19 @@ domain there shortly. We hope this will bring more attention to a great
resource, and you'll get a local copy with your local documentation.

Second, back in Rust 1.23, we talked about the change from Hoedown to
pulldown-cmark. In Rust 1.25, pulldown-cmark is now the default rendering.
After years, we have finally removed the last bit of C from rustdoc, and
properly follow the CommonMark spec.
pulldown-cmark. In Rust 1.25, pulldown-cmark is now the default rendering. We
have finally removed the last bit of C from rustdoc, and now properly follow
the CommonMark spec.

Finally, in [RFC 1358], `#[repr(align(x))]` was accepted. In Rust
1.25, [it is now stable]! This attribute lets you set the [alignment]
of your `struct`s:

```rust
struct NotAligned(i32);
struct Number(i32);

assert_eq!(std::mem::align_of::<NotAligned>(), 4);
assert_eq!(std::mem::size_of::<NotAligned>(), 4);
assert_eq!(std::mem::align_of::<Number>(), 4);
assert_eq!(std::mem::size_of::<Number>(), 4);

#[repr(align(16))]
struct Align16(i32);
Expand All @@ -93,7 +93,6 @@ can be very important!
[it is now stable]: /~https://github.com/rust-lang/rust/pull/47006
[alignment]: https://en.wikipedia.org/wiki/Data_structure_alignment


See the [detailed release notes][notes] for more.

### Library stabilizations
Expand All @@ -110,9 +109,9 @@ type for you!
`libcore` has [gained a `time` module](https://doc.rust-lang.org/core/time/),
containing the `Duration` type previously only available in `libstd`.

Additionally, the `new`, `from_secs`, `from_milis`, `from_micros`, and `from_nanos`
functions associated with `Duration` were made `const fn`s, allowing them to be used
to create a `Duration` as a constant expression.
Additionally, the `from_secs`, and `from_milis` functions associated with
`Duration` were made `const fn`s, allowing them to be used to create a
`Duration` as a constant expression.

See the [detailed release notes][notes] for more.

Expand Down Expand Up @@ -143,12 +142,13 @@ more](/~https://github.com/rust-lang/cargo/pull/5013).

Many users love `cargo doc`, a way to generate local documentation for their
Cargo projects. [It's getting a huge speed
bump](/~https://github.com/rust-lang/cargo/pull/5013) in this release, as now,
it uses `cargo check`, rather than a full `cargo build`.
bump](/~https://github.com/rust-lang/cargo/pull/4976) in this release, as now,
it uses `cargo check`, rather than a full `cargo build`, so some scenarios
will get faster.

Additionally, checkouts of git dependencies [should be a lot
faster](/~https://github.com/rust-lang/cargo/pull/4919), thanks to the use of
hard links where possible.
hard links when possible.

See the [detailed release notes][notes] for more.

Expand Down