|
| 1 | +# T-lang meeting agenda |
| 2 | + |
| 3 | +* Meeting date 2020-10-19 |
| 4 | + |
| 5 | +## Attendance |
| 6 | + |
| 7 | +* Team members: Niko, Josh, scottmcm, pnkfelix |
| 8 | +* Others: simulacrum, connor horman |
| 9 | + |
| 10 | +## Before meeting checklist |
| 11 | + |
| 12 | +* [x] Update the project board with new proposals |
| 13 | +* [x] Update the project board with new RFCs |
| 14 | + |
| 15 | +## Pending proposals |
| 16 | + - "Restrict promotion to infallible operations" [lang-team#58](https://github.com/rust-lang/lang-team/issues/58) |
| 17 | + - can possibly move to a design note until we get an RFC |
| 18 | + - niko to reach out to ralf and check in on how to handle |
| 19 | + - "MCP: pub(macro)" [lang-team#59](https://github.com/rust-lang/lang-team/issues/59) |
| 20 | + - agree that this problem needs solving |
| 21 | + - might be a good use for wishlist to try and find people |
| 22 | + - (done) |
| 23 | + - "Types as const Parameters" [lang-team#61](https://github.com/rust-lang/lang-team/issues/61) |
| 24 | + - potentially nice simplification in the future; the idea of reifying more of type system into values is interesting |
| 25 | + - but builds on const generics, which are still in progress |
| 26 | + - lots of unknowns (e.g., how to get access to the "values", convert them back into types, etc) |
| 27 | + - scott to write a move to close and tag as FCP |
| 28 | + |
| 29 | +## Design meeting planning |
| 30 | + |
| 31 | +- Getting consensus on lang team membership expectations (could do async) |
| 32 | + - [draft document](https://hackmd.io/qyfBQdcASom9Ab8TNmbdKg?view) |
| 33 | +- Lang team process tweaks (seconding/objections) |
| 34 | + - libs team has proposed [this charter](https://github.com/rust-lang/rfcs/pull/2979), has a lot of overlap compiler/lang |
| 35 | + - using seconding for approving MCP / proposal |
| 36 | + - using seconding to close/postpone RFCs |
| 37 | + - scheduling of design meetings, how to do it better |
| 38 | +- Discuss RFC 2580 (Pointer metadata and vtable) 55 |
| 39 | + - |
| 40 | +- Schedule invited discussion with authors of Rust paper |
| 41 | + - https://github.com/rust-lang/lang-team/issues/53 |
| 42 | + - following up on [this PLDI paper](https://cseweb.ucsd.edu/~yiying/RustStudy-PLDI20.pdf), to discuss sources of bugs and possible solutions |
| 43 | +- Backlog Bonanza |
| 44 | + - This week |
| 45 | + |
| 46 | +* Niko to follow up with a proposed schedule |
| 47 | + |
| 48 | +## Project board review |
| 49 | + |
| 50 | +Review the [Lang team project board](https://github.com/rust-lang/lang-team/projects/2) and get updates |
| 51 | + |
| 52 | +## Nominated RFCs |
| 53 | + - "RFC: -C export-executable-symbols" [rfcs#2841](https://github.com/rust-lang/rfcs/pull/2841) |
| 54 | + - "RFC: Supertrait item shadowing" [rfcs#2845](https://github.com/rust-lang/rfcs/pull/2845) |
| 55 | + - scottmcm read it and found it basically does all the things it should, discusses the key problems |
| 56 | + - most interesting thing: if you bound your generic to `T: Super`, `T: Sub`, `T: Super + Sub`, each has distinct meanings |
| 57 | + - `foo.bar()` would pick the method from super in the 1st case, from sub in the 2nd case, and be ambiguous in the 3rd case |
| 58 | + - also what happens from `T: Foo + Bar` where they share a method |
| 59 | + - presumably also applies to `T::Item` expansion |
| 60 | + - wait for boats to make a call whether to fcp merge |
| 61 | + |
| 62 | +## P-high issues on rust-lang/rust |
| 63 | + - "New "warning incompatible with previous forbid in same scope" error" [rust#77713](https://github.com/rust-lang/rust/issues/77713) |
| 64 | + |
| 65 | +## Nominated PRs and issues on rust-lang/rust |
| 66 | + - "Switch `mutable_borrow_reservation_conflict` lint to deny by default" [rust#76104](https://github.com/rust-lang/rust/pull/76104) |
| 67 | + - "`use dep1::foo as dep1` is considered ambiguous on nightly but not beta" [rust#77586](https://github.com/rust-lang/rust/issues/77586) |
| 68 | + - "New "warning incompatible with previous forbid in same scope" error" [rust#77713](https://github.com/rust-lang/rust/issues/77713) |
| 69 | + - "repr(transparent) on generic type skips "exactly one non-zero-sized field" check" [rust#77841](https://github.com/rust-lang/rust/issues/77841) |
| 70 | + - "Tracking issue for `X..`, `..X`, and `..=X` (`#![feature(half_open_range_patterns)]`)" [rust#67264](https://github.com/rust-lang/rust/issues/67264#) |
0 commit comments