Mara Bos

> I think hooks are going to be quite prone to potential deadlocks. That's not a blocker for doing this, just something that'll need to be documented. It'd be quite...

@ian-h-chamberlain Yeah, that possibility is mentioned in one of the unresolved questions in the RFC: > - Should the hook be able to access/configure more information about the child thread?...

We discussed this in the libs-api meeting; this seems ready for FCP. @rfcbot merge

Tracking issue: https://github.com/rust-lang/rust/issues/132951

We briefly discussed this in the lib-api meeting. This seems fine, but we thought it is important to consider if this could just be a non-edition change, considering how rare...

We discussed this again in the libs-api meeting. We think it's fine if `assert!()` no longer supports `&bool` (and other `Not` types) in the next edition. It might be worth...

Small nit: Numbers like `$1,000` can be slightly confusing (or at least annoying to read) for those who use the comma as a decimal separator rather than as thousand separator....

> Is there a situation under which this would not be better off as an associated constant? #105917 is an interesting case to think about: io::Chain. When chaining one stream...

> Please report your case here Merging #74532 just now ran into this problem. I worked around it by using `()` as dummy type: ```diff - let [] = [();...

@sdroege That's certainly a possibility and not incompatible with this RFC. The "future possibilities" section already mentions the possibility of adding more information in a separate (optional / debug) section,...