# Libs Meeting 2020-07-28

###### tags: `Libs Meetings` `Minutes`

## Agenda

- What are we working on? Are there any issues or RFCs we need input on?
- https://forge.rust-lang.org/libs/index.html#useful-github-queries
- Error handling group: https://github.com/rust-lang/rfcs/pull/2965
- Reading into uninit buffers: https://github.com/rust-lang/rfcs/pull/2930
- Lazy types: https://github.com/rust-lang/rfcs/pull/2788
- Any that have been sitting for a while?
- How do we like the std impl vs api split with compiler?
- What about crates like compiler-builtins and stdarch?
- Come up with a Libs team charter
- How should we organize going forward?
- Do we need a libs repo? What should be in it?
- Are there any project groups we should spin up?
- **Come up with a MCP for the rest of the team**

## Notes

- std-like libs:
- compiler-builtins
- stdarch
- hashbrown
- parking-lot
- log
- regex
- backtrace

- what should libs do?
- std is one of the easiest places to get started: easiest point of entry
- what are we lacking? Just no guidance on where to start

- using libs in std
- hasbrown and backtrace have evolving external APIs and stable API in std
- should we do more of this?

- unifying std
- needs lots of design work
- Error trait in core

- better shepherding of stabilisation
- do an audit of unstable libs features
- Try trait etc

- audit of libs crates
- who's maintaining them?

- MCP process

- bootstrap libs docs

- 2021 edition
- anything we can/want to do?
- possibly prelude changes
- fixing Range type
- libs perspective on various things