Loading...

​​T-Lang Meeting: Current meeting

​​Action item

• ​​Niko to reach out to wg-grammar around writing up a “what is status” thing

• ​​Niko to comment on https://github.com/rust-lang/rust/pull/74622 to say that this feels like largely libs call but we’d like consistency with print!​ and panic!​ in terms of when something is a format string or not

• ​​Josh to comment on  Tracking issue for RFC 2137: Support defining C-compatible variadic functions in Rust #44930  that we are in favor once associated fn support lands and bakes for 1 release

• ​​Josh to comment on #74754 

• ​​scottmcm to follow up on RFC: Overconstraining and omitting `unsafe` in impls of `unsafe` trait methods #2316 

​​Agenda

• ​​Add new MCPs and meeting proposals to the Lang Team Project Board

• ​​Review newly created RFCs

• ​​Review Lang Team Project Board:

• ​​Active items

• ​​Major Change Proposals

• ​​Meeting Proposals

• ​​Review P-high issues

• ​​Review Nominated PRs

• ​​Review Nominated issues

• ​​Review Nominated RFCs

• ​​Review rfcbot pending list

• ​​Review pending Project Proposals and generate a Project Proposal Report

​​Notes from meeting (2020-08-17):

​​make `ConstEvaluatable` more strict #74595 

​​It is less bad than I thought, so this works

​​fn test<T: Bar>() {

​​    let _ = [0; T::ASSOC];

​​}

​​


​​trait Bar {}

​​


​​impl Bar for u16 {}

​​impl Bar for (u8, u8) {}

​​


​​trait Fez {

​​    const ASSOC: usize;

​​}

​​


​​impl<T> Fez for T {

​​    const ASSOC: usize = 4;

​​}

​​but this breaks:

​​fn test<T: Bar>() {

​​    let _ = [0; T::ASSOC];

​​}

​​


​​trait Bar {

​​    const ASSOC: usize;

​​}

​​


​​impl Bar for u16 {

​​    const ASSOC: usize = 4;