惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

The GitHub Blog
The GitHub Blog
Engineering at Meta
Engineering at Meta
博客园 - 聂微东
博客园 - Franky
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
雷峰网
雷峰网
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
L
LangChain Blog
WordPress大学
WordPress大学
H
Help Net Security
H
Hackread – Cybersecurity News, Data Breaches, AI and More
Y
Y Combinator Blog
Blog — PlanetScale
Blog — PlanetScale
MyScale Blog
MyScale Blog
IT之家
IT之家
酷 壳 – CoolShell
酷 壳 – CoolShell
罗磊的独立博客
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
有赞技术团队
有赞技术团队
Apple Machine Learning Research
Apple Machine Learning Research
云风的 BLOG
云风的 BLOG
博客园 - 【当耐特】
P
Proofpoint News Feed
D
DataBreaches.Net

Rust Blog

Security Advisory for Cargo (CVE-2026-5223) | Rust Blog Security Advisory for Cargo (CVE-2026-5222) | Rust Blog Project goals update — April 2026 (end of 2025H2) | Rust Blog Rust is participating in Outreachy | Rust Blog Raising the baseline for the `nvptx64-nvidia-cuda` target | Rust Blog Announcing Google Summer of Code 2026 selected projects | Rust Blog Announcing Rust 1.95.0 | Rust Blog docs.rs: building fewer targets by default | Rust Blog Changes to WebAssembly targets and handling undefined symbols | Rust Blog Announcing Rust 1.94.1 | Rust Blog Security advisory for Cargo | Rust Blog What we heard about Rust's challenges | Rust Blog Call for Testing: Build Dir Layout v2 | Rust Blog Announcing rustup 1.29.0 | Rust Blog Announcing Rust 1.94.0 | Rust Blog 2025 State of Rust Survey Results | Rust Blog Rust debugging survey 2026 | Rust Blog Update on the October 15, 2018 incident on crates.io Announcing Rust 1.29.2 Announcing Rust 1.29 Announcing Rust 1.28 What is Rust 2018? Announcing Rust 1.27.2 Announcing Rust 1.27.1 Security Advisory for rustdoc Announcing Rust 1.27 Announcing Rust 1.26.2 Announcing Rust 1.26.1 Rust turns three Announcing Rust 1.26
Lang Team Design Meetings | Inside Rust Blog
Niko Matsakis on behalf of the language team · 2020-01-10 · via Rust Blog

Hi all! I wanted to give a quick update about the lang team. We're starting something new this year: a regular design meeting. The idea of the design meeting is that it's a time for us to have in-depth discussions on some particular topic. This might be a burning problem that we've discovered, an update on some existing design work, or a forward looking proposal.

The meetings will be scheduled in advance. Ideally, each meeting should also have a blog post before-hand giving background material, although that may be difficult to achieve in practice. Similarly, after each meeting, we'll typically post minutes and a recording, and ideally try to write up a summary blog post with major points. (Sometimes recordings are hard to achieve, either for technical reasons or because we wanted the ability to discuss more sensitive topics.)

The meetings are open for anyone to listen in and attend. They generally take place on Mondays at "noon Boston time" -- but for the precise scheduling you should check the lang team calendar. We'll try to keep the calendar up to date with the topic to be discussed in each meeting, as well. Meetings might not happen every week, if we don't have a topic in mind.

First design meeting

Our first design meeting was actually last Monday! We discussed the soundness hole that was found some time ago in Pin. You can read the minutes from our discussion and a recording is also available. You might also find it easier to read the comments in the internals thread. The good news is that we seem to be centralizing on a solution based on negative impls.

Next design meeting

The next design meeting will take place this coming Monday. The topic will be how to fix rust-lang/rust#57893, which is a soundness bug related to dyn types. There is a prepared writeup describing the problem and a possible solution to guide the meeting. It is maybe worth noting that one of the proposed solutions involved a Rust 2021 edition as well (although there are smaller, more targeted fixes that do not require a new edition).

Design meetings after that

The next two weeks are likely to not have design meetings:

  • January 20th is Martin Luther King, Jr. day in the US.
  • January 27th is the Mozilla All Hands.

As a result, in both cases, many of the lang team members will be unable to attend.