mark-simulacrum

6 ms·

1.
by mark-simulacrum 7y ago
Thanks for pointing this out! Unfortunately, unlike most of our docs we don't yet have testing in place for the code examples on the blog. I've just pushed up a fix though so once that propagates this should be fixed.
2.
Rust 1.40(blog.rust-lang.org)
430 points by mark-simulacrum 7y ago|150 comments
3.
Rust 1.38.0(blog.rust-lang.org)
83 points by mark-simulacrum 7y ago|7 comments
4.
Announcing Rust 1.36.0(blog.rust-lang.org)
353 points by mark-simulacrum 7y ago|180 comments
5.
by mark-simulacrum 8y ago
We're going to publish that soon -- it needs to be generated after the release is tagged and it took longer today. We'll edit the blog post when it's ready to go.
6.
Announcing Rust 1.30.1(blog.rust-lang.org)
6 points by mark-simulacrum 8y ago|0 comments
7.
by mark-simulacrum 8y ago
For the initial release, NLL will be enabled in "migration" mode in 2018 only. `#![feature(nll)]` will continue to be available -- that hard-enables MIR borrowck instead of the migration mode. (edit: to be clear, the feature gate
8.
by mark-simulacrum 8y ago
The future use for this will be to allow calling methods/functions/macros from 2015 edition code in 2018, where some additional keywords have been reserved. For example if you are using a crate with "dyn" as a method nam
9.
Announcing Rust 1.29.2(blog.rust-lang.org)
7 points by mark-simulacrum 8y ago|0 comments
10.
by mark-simulacrum 8y ago
Depending on what you're doing, there's often a few different approaches to reducing compile times. First of all, if you're going to be running (small) tests, then it may be beneficial to enable incremental with `--incrementa