---
# System prepended metadata

title: T-style triage meeting 2024-06-26
tags: [triage-meeting, minutes, T-style]

---

---
title: T-style triage meeting 2024-06-26
tags: ["T-style", "triage-meeting", "minutes"]
date: 2024-06-26
discussion: https://rust-lang.zulipchat.com/#narrow/stream/346005-t-style/topic/meeting.202024-06-26
url: https://hackmd.io/hYEbuR2dQn6_SIaFVirTLw
---

# T-style meeting agenda

- Meeting date: 2024-06-26

## Attendance

- People: Caleb, TC, Josh

## Meeting roles

- Facilitator: TC
- Minutes: TC

## Check-in

(Not minuted.)

## Scheduled design meetings

None.

Update these [here](https://github.com/orgs/rust-lang/projects/38/views/1).

## Proposed design meetings

None.

Update these [here](https://github.com/orgs/rust-lang/projects/38/views/1).

## Announcements or custom items

### Project Goals (and 2024H2 in particular)

Josh: We should talk about whether there are things that style (or `rustfmt`) might want to include for that.

https://github.com/rust-lang/rust-project-goals

(Discussion about the background of project goals.)

Caleb: I'd probably prefer to delay to the next round.  We could consider, e.g. chains and the more complexity-oriented approach we had discussed.

Josh: Agreed that larger things like complexity-based formatting would be a good fit for project goals, and that it's probably a next year sort of thing.

TC: Given that bandwidth is such a key limitation, and that so much falls on Caleb's shoulders, and given simultaneously how important tools like `rustfmt` are to the ecosystem, I wonder about possibly adding an unowned team goal for "expand `rustfmt` maintainership" that would discuss the bandwidth limitations and what some of the benefits of removing it would be, and whether that could be an effective mechanism for supporting the Foundation in seeking resources to help make that happen.

(Discussion about that.)

(The meeting ended here.)

---

## Nominated RFCs, PRs, and issues

### "Tracking Issue for RFC 3484: Unsafe Extern Blocks" rust#123743

**Link:** https://github.com/rust-lang/rust/issues/123743

### "Tracking Issue for Rust 2024: rustfmt enable `overflow_delimited_expr`" rust#123751

**Link:** https://github.com/rust-lang/rust/issues/123751

### "Tracking Issue for Rust 2024: rustfmt style editions" rust#123799

**Link:** https://github.com/rust-lang/rust/issues/123799

### "Tracking Issue for Rust 2024: rustfmt use version sort" rust#123800

**Link:** https://github.com/rust-lang/rust/issues/123800

### "Tracking Issue for Rust 2024: rustfmt change sort to Unicode-aware "non-lowercase before lowercase"" rust#123802

**Link:** https://github.com/rust-lang/rust/issues/123802

### "Tracking Issue for Rust 2024: rustfmt improve impl generics indentation " rust#124758

**Link:** https://github.com/rust-lang/rust/issues/124758

### "Tracking Issue for Rust 2024: rustfmt trailing comment alignment" rust#124760

**Link:** https://github.com/rust-lang/rust/issues/124760

### "Tracking Issue for Rust 2024: rustfmt raw identifier sorting" rust#124764

**Link:** https://github.com/rust-lang/rust/issues/124764

### "Tracking Issue for Rust 2024: rustfmt closure body braces" rust#124767

**Link:** https://github.com/rust-lang/rust/issues/124767

### "`edition.md` is causing many conflicts" style-team#192

**Link:** https://github.com/rust-lang/style-team/issues/192

## Pending PRs on the style-team repo

None.

## RFCs waiting to be merged

None.

## `S-waiting-on-team`

None.

## Proposed FCPs

**Check your boxes!**

### "style-guide: Note that we don't account for comments in every possible place" rust#121762

**Link:** https://github.com/rust-lang/rust/pull/121762

## Active FCPs

### "Add nightly style guide section for `precise_capturing` `use<>` syntax" rust#126753

**Link:** https://github.com/rust-lang/rust/pull/126753

## P-critical issues

None.

## Check-out

(Not minuted.)
