# Libs Meeting 2021-10-27
###### tags: `Libs Meetings` `Minutes`
**Meeting Link**: https://meet.jit.si/rust-libs-meeting-ujepnbwg2lzqgt6wvrndwimi
**Attendees**: Amanieu, Jane, Josh Stone, Mara, Mark, The 8472
## Agenda
- [Open Action Items](https://hackmd.io/Uehlc0qUQfWfvY1swYWRgQ)
- Triage
- Anything else?
- Clarify license situation with compiler-builtins (https://github.com/rust-lang/compiler-builtins/issues/307)
- Something for the foundation?
- Same issue with rustc_apfloat (or w/e it was called).
- No action for now. Josh to send Nell an email.
> [name=Josh Stone] Prioritization and Regressions seem to be for `T-libs-api` -- acked, intentional
## Triage
### FCPs
1 open T-libs FCPs:
- [[merge 88714](https://github.com/rust-lang/rust/issues/88714#issuecomment-950895535)] *use CLOCK\_BOOTTIME in Instant::now* - (3 checkboxes left)
### Critical
None
### Backports
None
### Prioritization Requested
- [3 `rust-lang/rust` `T-libs-api` `I-prioritize` items](https://github.com/rust-lang/rust/issues?q=label:T-libs-api+label:I-prioritize+is:open)
- [[74215](https://github.com/rust-lang/rust/issues/74215)] *Hash of \`Discriminant\` now produces different results across CPU architectures*
- We should probably just document that this is not stable over {compiler versions, architectures, builds? ..}.
- [[90263](https://github.com/rust-lang/rust/issues/90263)] *Regression in File::read\_to\_end on 1.57.0 Nightly*
- We call statx with NULL, which is not allowed. The *syscall* might just cleanly return EINVAL, but the libc wrapper might not like it as much.
- Not just 'life before main', this is 'life before the dynamic linker'
- [[90320](https://github.com/rust-lang/rust/issues/90320)] *regression: abs\_diff conflict leading to compilation failures*
### Nominated
- [1 `rust-lang/rust` `T-libs` `I-nominated` items](https://github.com/rust-lang/rust/issues?q=label:T-libs+label:I-nominated+is:open)
- [[90012](https://github.com/rust-lang/rust/issues/90012)] *Re\-enable debug checks in \`copy\[\_nonoverlapping\]\`*
- Question from oli: Using const select okay with T-libs? Yes, up to const-eval-wg to evaluate the risks. (Debug asserts like in this PR are low/no risk.)
- [1 `rust-lang/rust` `T-libs` `I-libs-nominated` items](https://github.com/rust-lang/rust/issues?q=label:T-libs+label:I-libs-nominated+is:open)
- [[88716](https://github.com/rust-lang/rust/issues/88716)] *linux: std::process, insecure dropping of ancillary groups*
- Josh to look at it in detail.
- [1 `rust-lang/libs-team` `T-libs` `I-nominated` items](https://github.com/rust-lang/libs-team/issues?q=label:T-libs+label:I-nominated+is:open)
- [[28](https://github.com/rust-lang/libs-team/issues/28)] *Experts Map*
### Regressions
- [1 `rust-lang/rust` `T-libs-api` `regression-from-stable-to-beta` items](https://github.com/rust-lang/rust/issues?q=label:T-libs-api+label:regression-from-stable-to-beta+is:open)
- [[90322](https://github.com/rust-lang/rust/issues/90322)] *regression: alloc::prelude removed*
- Acceptable. Close.
## Actions
- [ ] Reply to all issues/PRs discussed in this meeting, or add them to the [open action items](https://hackmd.io/Uehlc0qUQfWfvY1swYWRgQ).
_Generated by [fully-automatic-rust-libs-team-triage-meeting-agenda-generator](https://github.com/rust-lang/libs-team/tree/main/tools/agenda-generator)_