Tracking Issue for the Rust specification

[m-ou-se]

This is a tracking issue for rust-lang/rfcs#3355

About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

Steps / History

• Decide to start a Rust specification
  • Blog post: https://blog.m-ou.se/rust-standard/
  • RFC: RFC: Start working on a Rust specification rfcs#3355
  • Foundation support: RFC: Start working on a Rust specification rfcs#3355 (comment)
  • Lang team approval: RFC: Start working on a Rust specification rfcs#3355 (comment)
  • Council approval: RFC: Start working on a Rust specification rfcs#3355 (comment)
• Hire the editor (Rust Foundation)
  • Define role: RFC: Start working on a Rust specification rfcs#3355 (comment)
  • Acquire budget
  • Find the right candidate
• Start a specification (sub)team (Language team)
  • Zulip topic: https://rust-lang.zulipchat.com/#narrow/stream/213817-t-lang/topic/Specification.20subteam
• Decide on the exact name/title of the document
  • https://rust-lang.zulipchat.com/#narrow/stream/399173-t-spec/topic/naming.20for.20team.20.28and.20document.29: "Rust specification"
• Write a specification draft chapter (Editor and specification team)
  • Connor's array chapter
  • Joel's array chapter
  • Mara's array chapter
• Get feedback on draft chapters
• Decide how to use existing documents (Rust Reference, Nomicon, Ferrocene Spec)
• Design rough top level structure of the document
  • https://rust-lang.zulipchat.com/#narrow/stream/399173-t-spec/topic/Structure.3A.20chapters/near/420245542
  • Meeting with lang team: https://hackmd.io/UetDs_P1Sgmj8BEiWaXB5g
  • Ask t-opsem for input: https://rust-lang.zulipchat.com/#narrow/stream/136281-t-opsem/topic/Question.20from.20t-spec
  • Ask t-types for input: https://rust-lang.zulipchat.com/#narrow/stream/144729-t-types/topic/Question.20from.20t-spec
• Discuss work on specifying libcore
  • Meeting: https://hackmd.io/2nbylOlGTKmFKB0atr7Lrg
• Pick a license
  • Meeting: https://hackmd.io/2nbylOlGTKmFKB0atr7Lrg
  • Decision: Add a license spec#14
• Learn more about MiniRust and how to use that in the spec (in progress)
• Tooling (in progress)
  • Decide to use (extended) markdown
  • ...
• Write, review, and edit chapters (in progress)
  • ...
• Approval process to make chapters official
• ...

[traviscross]

@rustbot labels -I-lang-nominated

I'm going to remove the nomination as, while this is an important initiative for the lang team to track, there's not a specific question or request for a next step from the lang team right now. Whenever there is such a thing, of course, please nominate that.

[rmcnew]

From https://blog.rust-lang.org/inside-rust/2023/11/15/spec-vision.html, it seems that the "Hire the editor" and "Start a specification team" tasks are complete.

[ehuss]

Thanks @rmcnew, it should be updated now