Skip to content

Tracking issue for Rust working groups #54445

@nikomatsakis

Description

@nikomatsakis

This is a temporary tracking issue that exists to track the full set of Rust Working Groups. For each working group, we track the chat channel, associated team, as well as a short description of its purpose.

Definition: A Rust Working Group is a set of people working at common purpose. Working Groups are associated with a Rust team. Unlike a Rust Team, Working Groups don't have "formal decision making power", though often they are charged with drawing up recommendations, RFCs, or other documents for the teams (which is then intended to make the final decision).

Domain Working Groups

Networking services

Scope: Focusing on the end-to-end experience for both sync and async networking code, in coordination with the growing ecosystem in this space.
Contact(s): @withoutboats and @cramertj

WebAssembly

Scope: Focusing on the end-to-end experience of embedding Rust code in JS libraries and apps via WebAssembly.

Contact(s): @fitzgen
Get involved: https://github.com/rustwasm/team#get-involved

CLI Apps

Scope: Focusing on the end-to-end experience of writing CLI apps, both large and small, in Rust.

Contact(s): @killercup

Embedded Devices

Scope: Focusing on the end-to-end experience of using Rust in resource-constrained environments and non-traditional platforms.

Contact(s): @japaric

Lang and Compiler Team Working Groups

WG-NLL

Scope: Implementing the new MIR-based borrow check and non-lexical lifetimes. See the tracking issue for more information.

Chat channel: The wg-nll stream on Zulip.

Contact(s): @nikomatsakis and @pnkfelix

WG-UCG

Scope: Working out the "Unsafe Code Guidelines", which define what kind of behavior unsafe code can and cannot do. The unsafe-code-guidelines repository is where most of the discussion takes place (see the README, which explains the general setup, and the issues).

Chat channel: The wg-unsafe-code-guidelines stream on Zulip is used for coordination.

Contact(s): @nikomatsakis and @avadacatavra

WG-Grammar

Scope: Working out a the official, formal grammar for Rust and validating it against existing implementations.
See the announcement thread for more details.

Chat Channel: #wg-grammar on Discord

Contact(s): @Centril and @qmx

WG-Traits

Scope: Revamping the rustc trait implementation to follow the Chalk approach.

Chat Channel: There is a #wg-traits on Discord, but the group is currently on hiatus until Rust 2018 ships. =)

Contact(s): @nikomatsakis

WG-Compiler-Performance

Scope: Improving rustc compilation performance (build times).

Chat Channel: There is a #wg-compiler-performance on Discord, but the group is currently somewhat inactive.

Contact(s): @nikomatsakis

WG-Codegen

Scope: Improving code generated by rustc. Announcement thread.

Chat Channel: #wg-codegen on IRC and probably elsewhere too.

Contact(s): @nox

Metadata

Metadata

Assignees

No one assigned

    Labels

    C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCT-coreRelevant to the core team, which will review and decide on the PR/issue.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions