|
| 1 | +--- |
| 2 | +title: Triage meeting 2021-10-19 |
| 3 | +tags: triage-meeting |
| 4 | +--- |
| 5 | + |
| 6 | +# T-lang meeting agenda |
| 7 | + |
| 8 | +* Meeting date: 2021-10-19 |
| 9 | + |
| 10 | +## Attendance |
| 11 | + |
| 12 | +* Team members: Niko, Taylor, Felix |
| 13 | +* Others: Mark |
| 14 | + |
| 15 | +## Meeting roles |
| 16 | + |
| 17 | +* Action item scribe: simulacrum |
| 18 | +* Note-taker: Niko |
| 19 | + |
| 20 | +## Scheduled meetings |
| 21 | +- Tomorrow: "Dyn upcasting, safety considerations" [lang-team#119](https://github.com/rust-lang/lang-team/issues/119) |
| 22 | + - On Zulip! |
| 23 | +- "Never allow unwinding from Drop impls" [lang-team#97](https://github.com/rust-lang/lang-team/issues/97) |
| 24 | + |
| 25 | +## Announcements or custom items |
| 26 | + |
| 27 | +(Meeting attendees, feel free to add items here!) |
| 28 | + |
| 29 | +* Mark: ~const stuff |
| 30 | + * Do we have a good understanding of this design? |
| 31 | + * e.g., https://github.com/rust-lang/rust/pull/86840 is adding a bunch of const impls |
| 32 | + * there's also https://doc.rust-lang.org/nightly/core/intrinsics/fn.const_eval_select.html which is interesting |
| 33 | + |
| 34 | +## Action item review |
| 35 | + |
| 36 | +* [Action items list](https://hackmd.io/gstfhtXYTHa3Jv-P_2RK7A) |
| 37 | + |
| 38 | +## Pending lang team project proposals |
| 39 | + |
| 40 | +### "negative impls integrated into coherence" lang-team#96 |
| 41 | + |
| 42 | +**Link:** https://github.com/rust-lang/lang-team/issues/96 |
| 43 | + |
| 44 | +* scottmcm as liaison |
| 45 | + |
| 46 | +### "Deprecate target_vendor " lang-team#102 |
| 47 | + |
| 48 | +**Link:** https://github.com/rust-lang/lang-team/issues/102 |
| 49 | + |
| 50 | +### "Async fundamentals initiative" lang-team#116 |
| 51 | + |
| 52 | +**Link:** https://github.com/rust-lang/lang-team/issues/116 |
| 53 | + |
| 54 | +* nikomatsakis or maybe cramertj as liaison |
| 55 | + |
| 56 | +### "Attribute for trusted external static declarations" lang-team#118 |
| 57 | + |
| 58 | +**Link:** https://github.com/rust-lang/lang-team/issues/118 |
| 59 | + |
| 60 | +### "Prototype Sync & Async Iterator Items (Minimal generators)" lang-team#121 |
| 61 | + |
| 62 | +**Link:** https://github.com/rust-lang/lang-team/issues/121 |
| 63 | + |
| 64 | +* pnkfelix as liaison |
| 65 | + |
| 66 | +### "Enum Variant Types" lang-team#122 |
| 67 | + |
| 68 | +**Link:** https://github.com/rust-lang/lang-team/issues/122 |
| 69 | + |
| 70 | +* Most people are in favor of this general direction |
| 71 | +* Is it a good thing to do now and does someone have time to see it through? |
| 72 | + |
| 73 | +## PRs on the lang-team repo |
| 74 | +### "Initial draft of copy ergonomics design note" lang-team#62 |
| 75 | + |
| 76 | +**Link:** https://github.com/rust-lang/lang-team/pull/62 |
| 77 | + |
| 78 | +* Mark to update this with a "maybe incomplete see ...comment..." disclaimer, bug someone to merge |
| 79 | +* maybe just merge them with a link to follow-up? |
| 80 | + |
| 81 | +### "Add draft of variadic notes" lang-team#76 |
| 82 | + |
| 83 | +**Link:** https://github.com/rust-lang/lang-team/pull/76 |
| 84 | + |
| 85 | +* Mark to update this with a "maybe incomplete see ...comment..." disclaimer, bug someone to merge |
| 86 | +* maybe just merge them with a link to follow-up? |
| 87 | + |
| 88 | +### "consensus decision making" lang-team#113 |
| 89 | + |
| 90 | +**Link:** https://github.com/rust-lang/lang-team/pull/113 |
| 91 | + |
| 92 | +* pnkfelix left a review |
| 93 | +* josh needs to respond |
| 94 | + |
| 95 | +## RFCs waiting to be merged |
| 96 | + |
| 97 | +None. |
| 98 | + |
| 99 | + |
| 100 | + |
| 101 | + |
| 102 | +## Proposed FCPs |
| 103 | + |
| 104 | +**Check your boxes!** |
| 105 | + |
| 106 | +### "Constrained Naked Functions" rfcs#2972 |
| 107 | + |
| 108 | +**Link:** https://github.com/rust-lang/rfcs/pull/2972 |
| 109 | + |
| 110 | +### "RFC: Add `target` configuration" rfcs#2991 |
| 111 | + |
| 112 | +**Link:** https://github.com/rust-lang/rfcs/pull/2991 |
| 113 | + |
| 114 | +* niko has pending action item |
| 115 | + |
| 116 | +### "Tracking Issue for `destructuring_assignment`" rust#71126 |
| 117 | + |
| 118 | +**Link:** https://github.com/rust-lang/rust/issues/71126 |
| 119 | + |
| 120 | +* [stabilization report](https://github.com/rust-lang/rust/issues/71126#issuecomment-941148058) |
| 121 | + |
| 122 | +### "Tracking issue for `#![feature(const_precise_live_drops)]`" rust#73255 |
| 123 | + |
| 124 | +**Link:** https://github.com/rust-lang/rust/issues/73255 |
| 125 | + |
| 126 | +* [stabilization report](https://github.com/rust-lang/rust/issues/73255#issuecomment-938086246) |
| 127 | +* [cramertj points out that we don't have any docs on this](https://github.com/rust-lang/rust/issues/73255#issuecomment-942783781) |
| 128 | + |
| 129 | +### "Tracking Issue for relaxed struct unsizing rules" rust#81793 |
| 130 | + |
| 131 | +**Link:** https://github.com/rust-lang/rust/issues/81793 |
| 132 | + |
| 133 | +### "Tracking Issue for const-initialized thread locals" rust#84223 |
| 134 | + |
| 135 | +**Link:** https://github.com/rust-lang/rust/issues/84223 |
| 136 | + |
| 137 | +### "Port clippy lint `redundant_field_names` to compiler" rust#87512 |
| 138 | + |
| 139 | +**Link:** https://github.com/rust-lang/rust/pull/87512 |
| 140 | + |
| 141 | +* FCP to close |
| 142 | + |
| 143 | +## Active FCPs |
| 144 | +### "negative impls integrated into coherence" lang-team#96 |
| 145 | + |
| 146 | +**Link:** https://github.com/rust-lang/lang-team/issues/96 |
| 147 | + |
| 148 | + |
| 149 | + |
| 150 | +## P-critical issues |
| 151 | + |
| 152 | +None. |
| 153 | + |
| 154 | + |
| 155 | + |
| 156 | + |
| 157 | +## Nominated RFCs, PRs and issues |
| 158 | +### "Tracking Issue for const-initialized thread locals" rust#84223 |
| 159 | + |
| 160 | +**Link:** https://github.com/rust-lang/rust/issues/84223 |
| 161 | + |
| 162 | +### "Stabilize built-in attribute macro `#[cfg_eval]`" rust#87221 |
| 163 | + |
| 164 | +**Link:** https://github.com/rust-lang/rust/pull/87221 |
| 165 | + |
| 166 | +### "Port clippy lint `redundant_field_names` to compiler" rust#87512 |
| 167 | + |
| 168 | +**Link:** https://github.com/rust-lang/rust/pull/87512 |
| 169 | + |
| 170 | +### "Which patterns on union fields should be considered safe?" rust#87520 |
| 171 | + |
| 172 | +**Link:** https://github.com/rust-lang/rust/issues/87520 |
| 173 | + |
| 174 | +### "Stabilize `const_raw_ptr_deref` for `*const T`" rust#89551 |
| 175 | + |
| 176 | +**Link:** https://github.com/rust-lang/rust/pull/89551 |
| 177 | + |
| 178 | +### "warn on must_use use on async fn's" rust#89610 |
| 179 | + |
| 180 | +**Link:** https://github.com/rust-lang/rust/pull/89610 |
| 181 | + |
| 182 | +Mark to write a comment saying lang team has no objection to adding this warning until such time as `#[must_use]` on an async function works (if ever). |
| 183 | + |
| 184 | +### "Re-enable debug checks in `copy[_nonoverlapping]`" rust#90012 |
| 185 | + |
| 186 | +**Link:** https://github.com/rust-lang/rust/issues/90012 |
| 187 | + |
| 188 | +Discussed and left a comment. General feeling is that this is a "best effort" check and it's ok to go forward, but we were not clear on the overall limits of the extent to which miri can check this. |
0 commit comments