1. Bluesky Feeds /
  2. Andrew Lilley Brinker /
  3. Rust Lang Deep Dives

Substantive discussions about the Rust language itself as a project — language design, RFCs, the compiler, type system, memory model, governance, and Rust's future direction. Excludes crate releases and ecosystem projects.

Feed on Bluesky

Feeds Stats

  • 💙 Liked by 11 users
  • 📅 Updated about 1 month ago
  • ⚙️ Provider attie.ai

Rust Lang Deep Dives Likes over time

Like count prediction
The feed Rust Lang Deep Dives has not gained any likes in the last month.

Feed Preview for Rust Lang Deep Dives

HackerNews Compilator
@hnbot.gsuscs.xyz
16 days ago
An alias-based formulation of the borrow checker (2018) smallcultfollowing.com/ba…
0
0
0
The Lobste.rs RSS feed
@lobsters-feed.bsky.social
16 days ago
Cylic trait implementations: motivation lobste.rs/s/zq9czz #rust #compilers #plt

smallcultfollowing.com

Cylic trait implementations: motivation

0
0
0
デイリーZennトレンド
@dailyzenntrends.bsky.social
15 days ago
今日のZennトレンド 型の表現力はタダ: Rustのニッチ最適化を追う【第3部: コンパイラ内部を読む】 Rustのニッチ最適化におけるコンパイラ内部の実装を解説しています。 型の有効値範囲(valid_range)の外側をニッチとして利用し、Option型のメモリサイズを最適化する仕組みです。 boolや参照、NonZeroU8などの有効範囲の定義から、Niche構造体によるニッチ値の決定、LLVM IRへの出力までの過程を追い、メモリ効率を高める実装詳細を明らかにしています。
型の表現力はタダ: Rustのニッチ最適化を追う【第3部: コンパイラ内部を読む】

zenn.dev

型の表現力はタダ: Rustのニッチ最適化を追う【第3部: コンパイラ内部を読む】

!この記事はシリーズの第3部です。第1部: メモリレイアウトの観察第2部: MIR・LLVM IR・ASMを追う第3部: コンパイラ内部を読む(本記事)第4部: ニッチ最適化の実践パターン はじめにこんにちは、moriです。ファスト株式会社にてRustを用いてデスクトップアプリケーション・バックエンドの開発を行っています。第1部では Option<NonZeroU8> が u8 と同じ

0
0
0
Hacker News Top 100 Bot (Unofficial)
@hn100.bsky.social
16 days ago
An alias-based formulation of the borrow checker (2018) Discussion
0
0
0
AstraKernel 💫
@astrakernel.bsky.social
21 days ago
🦀 rust-lang/rust is adopting an LLM policy > Because Rust governance doesn't work that way. We do not have a benevolent dictator who can say "No LLM-generated content, whether it be code or prose." or "AI is a tool, just like other tools we use" blog.rust-lang.org/inside-rust/... #rustlang
rust-lang/rust is adopting an LLM policy | Inside Rust Blog

blog.rust-lang.org

rust-lang/rust is adopting an LLM policy | Inside Rust Blog

Want to follow along with Rust development? Curious how you might get involved? Take a look!

1
2
12
Gene Conroy-Jones
@foursignalsdev.bsky.social
23 days ago
Rust's 2026-2027 goals replace Pin with Move/Forget traits. Type-level immobility and guaranteed destructors simplify async safety for self-referential futures and kernel code.
Rust Project Goals: Immobile types and guaranteed destructors

www.foursignals.dev

Rust Project Goals: Immobile types and guaranteed destructors

Four Signals — The Wire

0
0
0
sentinel auto
@sentinel-auto.bsky.social
16 days ago
💡 An alias-based formulation of the borrow checker (2018) Groq was unavailable, so this is a static fallback with no LLM-generated stance 🔗 smallcultfollowing.com/ba…
An alias-based formulation of the borrow checker (2018)
0
0
0
nikomatsakis
@nikomatsakis.com
16 days ago
Lately I've gotten kind of obsessed with the question of "how to manage cycles in Rust traits". I've begun to make real progress, so I decided to start blogging: smallcultfollowing.com/ba….

smallcultfollowing.com

Cylic trait implementations: motivation · baby steps

4
0
21
Gene Conroy-Jones
@foursignalsdev.bsky.social
23 days ago
Rust's 2026-2027 goals replace Pin with Move/Forget traits. Type-level immobility and guaranteed destructors simplify async safety for self-referential futures and kernel code.
Rust Project Goals: Immobile types and guaranteed destructors

www.foursignals.dev

Rust Project Goals: Immobile types and guaranteed destructors

Four Signals — The Wire

0
0
1
The Lobste.rs RSS feed
@lobsters-feed.bsky.social
10 days ago
Protecting the Rust standard library from accidental breakage lobste.rs/s/hnx6id #rust
Protecting the Rust standard library from accidental breakage

predr.ag

Protecting the Rust standard library from accidental breakage

How & why we're running cargo-semver-checks in Rust's CI

0
0
1
Ruslan Diachenko
@rdiachenko.bsky.social
20 days ago
Validation checks a value and often throws away what it learned. Parsing returns a type that keeps those guarantees. I wrote about "Parse, Don't Validate" in Rust: newtypes, boundary and shotgun parsing, a serde trap, and coding agents. rdiachenko.com/posts/rust/p... @thisweekinrust.bsky.social
Parse, Don't Validate, in Rust

rdiachenko.com

Parse, Don't Validate, in Rust

Validation throws away what it learned. Parsing returns it. In Rust, that moves invariants into the type system, where both developers and coding agents have to respect them.

0
0
2
Valdemar
@erk.dev
15 days ago
I have been thinking a lot about the RangeFrom type (n..) in Rust so I thought I would write up a bunch of history about to have somewhere to start a further discussion about it: erk.dev/2026/08/12/r...

erk.dev

RangeFrom, Part 1..: History and background

A probably too detailed look at the history of the RangeFrom type in Rust

0
1
8
sentinel auto
@sentinel-auto.bsky.social
16 days ago
💡 An alias-based formulation of the borrow checker (2018) Groq was unavailable, so this is a static fallback with no LLM-generated stance 🔗 smallcultfollowing.com/ba…
An alias-based formulation of the borrow checker (2018)
0
0
0
Gene Conroy-Jones
@foursignalsdev.bsky.social
17 days ago
Polonius, Rust's next-gen borrow checker, is now default on Nightly. It kills false positives in conditional branches and HashMap patterns. Benchmarks on top 10k crates show minimal compile-time regressions. Switch to Nightly and test…
Rust Borrow Checker 2.0 is Finally Here

www.foursignals.dev

Rust Borrow Checker 2.0 is Finally Here

Four Signals — The Wire

0
0
0
Shawn Chauhan
@shawnchauhan1.bsky.social
20 days ago
One of the most important open source projects in tech just told AI models what they're allowed to do. The Rust language maintainers published a new LLM policy on August 5. Models can help analyze, review, and refine code. They are not permitted to author it outright.
0
0
2
Hacker News RSS
@hn.rbrt.fr
23 days ago
Rust project goals: Immobile types and guaranteed destructors github.com/rust-lang/rust… news.ycombinator.com/item…
0
0
0
fratschi
@fratschi.bsky.social
20 days ago
A better borrow checker 😃 Ok, only on nightly, but I hope it will make it to stable soon. blog.rust-lang.org/2026/08/04/e...
Enabling the next iteration of the borrow checker on nightly | Rust Blog

blog.rust-lang.org

Enabling the next iteration of the borrow checker on nightly | Rust Blog

Empowering everyone to build reliable and efficient software.

0
1
4
Sedat Kapanoğlu
@ssg.dev
22 days ago
“It's fine to use LLMs to answer questions, analyze, distill, refine, check, suggest, review. But not to create.”
rust-lang/rust is adopting an LLM policy | Inside Rust Blog

blog.rust-lang.org

rust-lang/rust is adopting an LLM policy | Inside Rust Blog

Want to follow along with Rust development? Curious how you might get involved? Take a look!

0
0
7
Hacker News Top 100 Bot (Unofficial)
@hn100.bsky.social
22 days ago
Enabling the next iteration of the borrow checker on nightly Discussion
0
0
0
Predrag Gruevski
@predr.ag
10 days ago
Rust CI now runs cargo-semver-checks to prevent accidental breakage in the standard library 🦀 If you're wondering why that's important and why it took 15kLoC+, this post is for you. predr.ag/blog/protect...
Protecting the Rust standard library from accidental breakage

predr.ag

Protecting the Rust standard library from accidental breakage

How & why we're running cargo-semver-checks in Rust's CI

0
11
60