Skip to content

RustChinaConf 2026

The schedule designed for the conversation.

October 15–17 in Shenzhen. The structure is published now so you can plan for the kind of time we are protecting; the individual sessions follow on September 25.

Programme release

The full schedule is published September 25.

This is an intentional planning state, not a missing agenda: we are holding the session list until CFP review is complete, while making the rhythms, tracks, and non-stage spaces clear in advance.

One session, 35 minutes

Enough time to make the useful part discussable.

25 min

Talk

A focused argument, implementation, or production lesson.

10 min

Conversation & Q&A

Questions stay in the room rather than becoming an afterthought.

Speakers are prepared for 25 minutes. To protect the following discussion, a talk that runs over will be stopped directly.

Three-day framework

The programme has five places to meet, not one stage to fill.

Each afternoon includes a 40-minute tea break. The time deliberately left off the main stage belongs to conversations, demos, and follow-up.

October 15

Opening the questions

  • Main conference sessions
  • Hallway conversations
  • Demo area
  • Office Hours
  • Themed lunch tables

40-minute afternoon tea break

October 16

Working through the details

  • Main conference sessions
  • Hallway conversations
  • Demo area
  • Office Hours
  • Themed lunch tables

40-minute afternoon tea break

October 17

Taking the work forward

  • Main conference sessions
  • Hallway conversations
  • Demo area
  • Office Hours
  • Themed lunch tables

40-minute afternoon tea break

Three tracks

The engineering questions the programme is being built around.

T1

Rust for AI

The systems layer beneath AI infrastructure and products.

  • Training data pipelines and object storage
  • AI-ready databases and streaming systems
  • PyO3 hot paths, agent runtimes, and MCP
  • Edge inference, engines, and heterogeneous GPU compute

T2

AI for Rust

How AI changes Rust practice, and where Rust makes AI-assisted engineering more dependable.

  • LLM-assisted C/C++ to Rust migration
  • AI-assisted unsafe audits and formal verification
  • rustc parallel compilation and incremental systems
  • rust-analyzer and supply-chain risks in generated code

T3

Rust in Production

Large-scale production Rust, including how AI-for-Rust work reaches real systems.

  • Rust for Linux and domestic kernels
  • Data and storage engine rebuilds
  • Network data planes, embedded volume production, and safety-critical certification
  • Governance and incident reviews in large codebases

Sponsored

When the full agenda is released, sponsored sessions will carry this label and appear separately from CFP-selected talks.