Legend for methods/intrinsics: blue is safe, red is unsafe. solid is stable, dashed is unstable digraph hierarchy { rankdir=LR nodesep=1.0 // increases the separation between nodes node [color=Red,fontname=Courier,shape=box] //All nodes will this shape and colour edge [color=Blue] //All the lines look like this transmute transmute_unchecked

Items from 2021-07-09 meeting [ ] proposed action: add ability to issue Public Service Announcements (PSAs) from rustup. [ ] proposed action: start adding links to pre-existing issues for the diagnostics emitted by "long-lived ICEs" [ ] edit: clarify distinction between "We need better visibility (or more advertisement within the teams) of when user-disruptive changes are scheduled to hit." and "We need better tracking of when certain ICE's start becoming more serious problems for our users." [ ] edit: why was "We need to stop unfixed ICEs from becoming problems that we never hear about." considered a separate Lesson? Just merge it with neighboring lesson. [ ] edit: for Need more testing of dev workflows, add Corrective Action that covers automated testing, e.g. something analogous to mw's incr-comp commit checker. [ ] proposal (from Wesley): I would really like to have a dedicated WG/team whatever of beta testers. They might also be a good candidate set of people for opt-in telemetry Items for 2021-07-02 meeting [x] Review Five Whys and Lessons Learned, get feedback on what other "Whys" are missing, what to elaborate on, and what to cut.

[x] "Aaron Ballman" aaron@aaronballman.com -- not on spreadsheet [x] "Abramo Bagnara" abramo.bagnara@gmail.com -- not on spreadsheet [x] "Alexander Kornienko" alexfh@google.com -- not on spreadsheet [x] "Alexey Samsonov" samsonov@google.com -- not on spreadsheet [x] "Alexey Samsonov" vonosmas@gmail.com -- not on spreadsheet [ ] "Alp Toker" alp@nuanti.com -- on spreadsheettwo commits cb4029110040c3655a66b5f423d328c749ba6a49 f907b891da1641034f0603b0c6bc00b7aa4d1f4a seems to just be running a spellchecker in both commits [x] "Andrea Di Biagio" Andrea_DiBiagio@sn.scee.net -- not on spreadsheet

Felix headshotBryan headshot Felix S. Klock (pnkfelix), Bryan Garza (bryangarza) Amazon Web Services Rust Platform Team demo source machine code

Notes for revision (see inline comments!) some customers will already have some of this context "dont bake me cake"at very least, add a design tradeoffs section, in particular "why not just instrument" how is this different from Kani / doesn't Kani already give me this? what is value proposition versus full-verification add customer-centric Potential Questions from Readers

see also krabcake goals and design :::info Meta info: What is the goal of this document, and who is its audience? Audience(s): people who need deep undertanding of the internals people who could contribute to this tool, and need guidance for how to do so. people designing/documenting the operational semantics of Rust may want to inspect the source code architecture of this tool as part of an ongoing dialogue between developers of Krabcake and the Rust T-opsem. :::

async fn foo(PAT: [u8; 10]) { /* ... */ } ==> fn foo(x: [u8; 10]) -> impl Future<...> { // ~~~~~~~~~~~ don't focus on the parameters // ... because // async {

Working through method breakage sequenceDiagram participant upstream as upstream,<br/>2015 edition<br/>provides trait `Tr1`<br/>with `foo()` method participant crate as crate<br/>calls `t.foo()` where `t`<br/>implements `Tr1`+`Tr2` participant stdlib as stdlib<br/>provides trait `Tr2` Note over crate: developed against Rust 2018 edition Note over crate,stdlib: (no `foo()` method available<br/> on `Tr2` at this time) crate ->> upstream: t.foo() Note over upstream,crate: (Currently sole resolution available)

Question/Topic Queue How do I add an entry pnkfelix: Put a title, prefixed by ##, and then on the next line, your name, colon, and a short prompt to start the conversation. Bug Minimization matt: are there any changes to compiler tooling since your blog post? pnkfelix: Yep, e.g. -Z everybody-loops was removed. Replaced every fn body with loop { }, has type !, and ! is subtype of every other type (at least informally).

# Notes on dominators ICE

Cloud Desktop Setup Instructions See oli-obk's doc: https://hackmd.io/VPGjaYD5Q6u8RbhouDCXWg How to bound RustcContributor::* facilitator time commitments One of pnkfelix's main concerns in soliciting people to help act as facilitators (instructors?) is how to predict (and set bounds on) workload. We can easily set bounds office-hour obligations (namely: just show up at the start time and answer questions for that set period) But a presentation needs one or two things: * a plan (i.e., the things you want to cover during the presentation)

Feature Name: improve-c-types-for-cross-language-cfi Start Date: 2022-07-25 RFC PR: rust-lang/rfcs#0000 Rust Issue: rust-lang/rust#0000 Improve C types for cross-language LLVM CFI support. Motivation This RFC is part of the LLVM Control Flow Integrity (CFI) Support for Rust, and is a requirement for cross-language LLVM CFI support.

RFC PR #3296: Improve C types for cross-language LLVM CFI support References Broader "LLVM Control Flow Integrity" Tracking issue https://github.com/rust-lang/rust/issues/89653 Papaevripides and Athanasopoulos (2020): "Exploting Mixed Binaries" (PDF) Mergendahl et al (2022): "Cross-Language Attacks" (PDF) RFC #3296 proposes to "identify" uses of C char and integer types at "time types are encoded". (PnkFelix didn't understand what the quoted terms were meant to mean on their first read, but they believe they understand it now, and can work with the RFC author revise their text to make this more immediately clear.)

RFC PR #3296: Improve C types for cross-language LLVM CFI support References Broader "LLVM Control Flow Integrity" Tracking issue https://github.com/rust-lang/rust/issues/89653 Papaevripides and Athanasopoulos (2020): "Exploting Mixed Binaries" (PDF) Mergendahl et al (2022): "Cross-Language Attacks" (PDF) RFC #3296 proposes to "identify" uses of C char and integer types at "time types are encoded". (PnkFelix didn't understand what the quoted terms were meant to mean on their first read, but they believe they understand it now, and can work with the RFC author revise their text to make this more immediately clear.)

Licensing Meeting 2022-09-29 [toc] Meeting Notes we want there to be as few barriers as possible for contributions ((?) especially from paid contributors (?)) our source code licensing situation is a bit of a mess we want our licensing situation to be as simple as possible, for the benefit of our contributors ideally, we'd like to aim for MIT/Apache 2.0 dual-licensed across the board

Question Set A https://github.com/rust-lang/rust/pull/96709#issuecomment-1181931456 poses the following example: The distinction between ensures clauses and where clauses. Given a trait like this: trait WidgetFactory { type Item<T>: Display

<!-- # Current lints and the above categories 1. [future-proofing][]: flagging code that a future release of Rust will reject (potentially edition-tied), 2. [error-heuristic][]: flagging sound code correlated with programmer error, 3. [uniformly-clean][]: enforcement of uniform coding style, and 4. [expressly-clean][]: educating the user about Rust features Lint | [future-proofing] | [error-heuristic] | [uniformly-clean] | [expressly-clean] ------|--------|--------|------|------

-- mode: compilation; default-directory: "~/Dev/Rust/ducere/" -- Compilation started at Sat Mar 26 11:53:27 cargo test Blocking waiting for file lock on build directory Compiling ducere v0.1.0 (/Users/pnkfelix/Dev/Rust/ducere) Finished test [unoptimized + debuginfo] target(s) in 2.40s Running unittests (target/debug/deps/ducere-80daeaf2c805f0e4) running 11 tests