はてなブックマーク

Good morning everyone! Leading up to the Rust 2018 edition release we’d like to showcase a new upcoming feature once a week to ensure it’s well tested and well vetted for the 2018 release, ensuring that everything goes smoothly at release time! Starting off this week I’d like to sound a call to arms for the module system changes in the 2018 edition! The module system changes in 2018 can largely be

The Rust teams having been working hard to implement features of the 2018 edition. Today we have reached an important milestone: we are announcing that we have an alpha-quality preview of the 2018 edition ready for testing and feedback. The preview presents a great opportunity for those of you using the stable channel to switch to nightly and try out how it feels to code in the new edition, both t

At the recent Rust work week in Berlin, we formed a working group to investigate formal methods in Rust. The scope of this working group ranges from projects like RustBelt that are intended to develop a formal foundation for the language to projects that will directly analyze Rust programs. Our goals are to provide a central location where we can gather and share information on ongoing efforts. As

Good morning Rustaceans! Hot off the heels of the Rust All Hands in Berlin last week we’ve had numerous discussions about the stabilization of Macros 2.0 and what we can have ready for the Rust 2018 release. I’d like to detail what we discussed here as well as solicit for your help in stabilizing a “Macros 1.2” in the upcoming 1.27 release possibly. All-hands recap In Berlin we had a session speci

This is the first newsletter of the Embedded WG! We will be releasing this newsletter on a bi-weekly basis, and we are looking to highlight new progress, celebrate cool projects, thank the community, and advertise projects that need help! If you want to mention something in the next newsletter, make sure to leave a comment on the issue! Highlights Tock-OS has released the 1.0 of their kernel, gott

Very nice! Is there any plan to enable #[target_feature] attributes for things other than functions? For example, I’d expect that applying #[target_feature] to a module or an impl would be the same as applying it to every function or method in that module or impl. Instead, it seems to currently result in an ICE. Yes, I know about this RFC, but I don’t think it’s the best approach either. I had in

My plan for parallelizing rustc basically is to allow use of Rayon anywhere in the compiler. If you’re unfamiliar with Rayon or need a refresher, I suggest you read http://smallcultfollowing.com/babysteps/blog/2015/12/18/rayon-data-parallelism-in-rust/. There are a number of loops in rustc which just iterates over all items in a crate and these should use Rayon iterators instead. Parallelizing the

It’s finally coming! We’re in the home stretch for landing the long-awaited impl Trait feature. impl Trait allows functions to accept and return values of unnamed types that implement some trait. Many longstanding bugs and ICEs have been fixed, and final syntax details are nearly resolved. With that in mind, we need help testing and experimenting with the feature before stabilizing. Please conside

One week ago, the “impl period” formally launched, with 35 initial workgroups! We have a global Gitter channel (with IRC bridge) and dedicated channels for each working group. It’s worth repeating that this effort is intended for people with all experience levels and interests — there really is something for everyone, and the WG leads are putting a ton of work into mentoring. So if you’ve ever tho

Rust has amazing potential to generate impressively fast projects. It seems like every week, we hear about new advancements in browsers, search engines, web servers, and more - all driven by the safety and performance that Rust provides. At the same time, compile times are a common complaint for the Rust compiler. As projects grow, the compile time pains also grow. This is doubly true for programm

Over the last few weeks incremental compilation has reached a level stability and performance where we think it is ready for more widespread testing. We invite everyone who is already using the nightly version of Rust to switch the feature on and enjoy the sometimes substantially reduced compile times. If you are using Cargo, you can opt into incremental compilation by setting the CARGO_INCREMENTA

Hi there! I’d like to provoke some discussion about what can be done for better interoperability between Rust and C++, especially when templates are involved. I think everybody around here is going to agree that easy Rust/C++ interop would be a boon for Rust adoption among the current C++ users. State of the art To recap, I know of three projects that currently offer some level of C++ interop: rus

Hi everyone, So I’ve been having some interesting conversations with @sunfishcode, and I wanted to talk about an idea that he floated to me and try to get some feedback. The idea is to add an alternate backend to LLVM based on Cretonne. Cretonne is a compiler IR, similar to LLVM, being implemented (in Rust!) for use with WASM. It is intended for use in SpiderMonkey, Mozilla’s JS engine. The idea i

Recently, Niko and I landed our first batch of changes in rethinking how we display compiler error messages. Error messages in Rust, especially ones like borrow checker errors, have a lot of moving parts to them. As a new user, the first time you see errors like this can be daunting. The information is there, but you have to wrap your head around it to know what to do next. We've got a new design

Discussions around the design and implementation of The Rust Programming Language

https://github.com/nrc/rustw (there are some screenshots in the README and a link to a demo (although it is very slow and lacks some functionality)). Rustw is an experiment I’ve been working on recently, it is still very early days, but I’d love to get some early feedback. It is a frontend for the Rust compiler (or Cargo) and is primarily designed to be a better way to present errors to the user.

Hi all. I’d like to introduce rustup, the fabulous new way to install and manage Rust toolchains. This is the successor to multirust, and began as multirust-rs by @Diggsey. Although there’s a lot of work yet to do on it, it is feature complete and I’d like to get some feedback. To try it just go to http://www.rustup.rs and follow the instructions - everything you need to know should be reachable f

Hey all! As many of you know, my summer internship’s primary project is to try to better specify and document all the fiddly details you need to understand to correctly write unsafe Rust code. My current primary effort for this is TURPL: The Unsafe Rust Programming Language. TURPL is meant to complement TRPL as an advanced text. What exactly should or should not be included in TURPL is currently u

It should come as no surprise that life lately has been dominated by the upcoming Rust 1.0 release. But now that the beta release is out the door, I’ve started to give some thought to what we ought to do next. Obviously, there is no shortage of good ideas out there for how to grow the language. Just as obviously, we need to be careful about what we implement and when we implement it. This post rep