Skip to content

RustChinaConf 2026

Call for Proposals

The RustChinaConf 2026 Call for Proposals opens today and closes on September 20, 2026, at 23:59 (UTC+8).

Programme design

Why reduce the programme to 30?

Last year's Hangzhou programme placed about 50 talks across two days and three parallel tracks. Sessions ran back-to-back for 20–30 minutes, with one 20-minute tea break for the whole day.

This year, every talk has room for discussion and Q&A afterwards, the afternoon tea break is 40 minutes, and the schedule deliberately leaves space beyond the stage.

Talks now occupy 46% of the day, compared with 71% last year. The recovered time is for hallway conversations, demos, office hours, and themed lunch tables.

For speakers, this is good news: a strong session is no longer compressed into a back-to-back slot. It has time to be heard, questioned, and continued in the room afterwards.

Three concurrent tracks

Rust and AI is the throughline.

The conference runs three parallel tracks. Choose the one that best frames your contribution; T3 does not have to be about AI, but practical AI-for-Rust adoption at scale remains especially relevant.

T1

Rust for AI

The systems layer of AI infrastructure: the foundations that make data, models, agents, and inference dependable and efficient.

Directions include

  • Training-data pipelines and object storage
  • Database and streaming-system adaptations for AI workloads
  • Rewriting PyO3 hot paths
  • Agent runtimes and MCP
  • On-device inference
  • Inference engines and heterogeneous GPU computing

T2

AI for Rust

How AI changes the act of writing Rust, and where Rust has an advantage in AI-assisted software engineering.

Directions include

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

T3

Rust in Production

Large-scale Rust adoption in production. AI is not required, but the production application of AI for Rust is of particular interest.

Directions include

  • Rust for Linux and domestic kernels
  • Data and storage-engine rewrites
  • Extreme network data-plane optimisation
  • Embedded mass production
  • Automotive and safety-critical certification
  • Engineering governance in large codebases and production incident reviews

Review principles

How we review

  1. 1. Information density

    How much can an attendee exchange 35 minutes for that they could not find by themselves?

  2. 2. Verifiability

    Code, benchmarks, and production data take priority over an opinion-only presentation.

  3. 3. Honesty

    Failure, trade-offs, and hard-won lessons take priority over a success story alone.

  4. 4. Scarcity

    We keep one talk for each substantially similar topic.

The review group is independent from sponsorship discussions. Sponsored sessions will be marked Sponsored on the schedule and presented separately from CFP selections; reviewers do not share in any sponsorship revenue.

Three things attendees will take away

Write three specific declarative sentences.

Weak example
Learn about Rust applications in databases.
Specific example
Know under which conditions the dynamic-dispatch cost of a trait object exceeds the compile-time cost of generic monomorphisation.

This is the highest-weighted part of review. If the three statements are not specific, the talk itself is probably not clear yet.

What happens after a rejection?

For strong proposals we cannot accept, we will proactively ask whether you would like to switch to a five-minute lightning talk or join a roundtable discussion.

Speaker benefits

  • A full conference pass, speaker lounge access, and speaker dinner
  • Travel and accommodation reimbursement, except for lightning talks and roundtables
  • The raw recording file, which speakers may publish themselves
  • A speaker-only conference swag package

Non-negotiable format

  • Each session is 35 minutes: 25 minutes of presentation and 10 minutes of discussion and Q&A. We will stop an overrun directly.
  • Chinese and English are treated equally, and every session has live captions.
  • Pre-recorded playback is not accepted. Speakers must attend and be able to participate for the full conference day of their session.
  • A company may submit no more than two talks and have at most one accepted.

Timeline

Key dates

MilestoneDate
Submissions openAugust 10
Submission deadlineSeptember 20, 2026 · 23:59 (UTC+8)
Acceptance notificationsBy September 25
Programme publishedSeptember 25
Slides dueOctober 10
ConferenceOctober 15–17 · Shenzhen

RustChinaConf 2026

Ready to submit?

Make the question concrete and make the trade-offs clear.

Submit a proposal