Get the latest tech news

Rust Needs an Official Specification

Can we currently reason about Rust code with absolute certainty? Not really, but we should be able to. In this article, we dive into the reasons why it may be time for a Rust specification.

In a sense, that is also the purpose of having a standard: creating a stable and reliable platform for building software where new features don't appear every three fortnights. And even though in C++11 (and beyond), so many changes have been made that C++ has almost morphed into a different language, the pace of innovation is much slower, and also much less gradual than currently allowed by the 6-week release cycle of the Rust compiler. As I've tried to show by analogy with C/C++, "going full ISO" would slow things down; leading to a large set of updates being rolled out every 5 years or so; and wresting control away from a process that is currently doing a fine job.

Get the Android app