HackMD
PEH 2021-04-12 Meeting Agenda
tags: Error Handling Minutes
- Previous Meeting: https://github.com/rust-lang/project-error-handling/blob/master/meetings/2021-03-15.md
- Action Items: https://hackmd.io/@rust-libs/Hyj7kRSld
- Book Planning Doc: https://cryptpad.fr/code/#/2/code/edit/1FhyaBOOANgdSTKA8xbYIt8t/
Agenda Items
- Review action items from last meeting
- Individual Status Updates
- Review Project Board Issues
- https://github.com/rust-lang/rust/issues/46871
- https://github.com/rust-lang/rust/pull/79692
- https://github.com/rust-lang/compiler-team/issues/410
- https://users.rust-lang.org/t/an-essay-of-checked-exceptions-in-rust/57769
- https://users.rust-lang.org/t/using-the-return-operator-in-the-match-expression-early-return-of-an-error/58025
Attendees
- Jane Lusby
- Jakub Duchniewicz
- Charles (Chas) Ellis O'Riley Jr.
Meeting Minutes (Jane)
Action Items Review
- blog post is currently waiting on feedback from Niko, meeting scheduled to discuss it on Friday, will probably need another revision after that conversation.
- Error diagram for book is coming along
- Termination trait has run into issues with specialization, also need to answer questions about the underlying representation.
- backtrace in core is having issues with lang items not being recognized, even for the initial PoC impl
- Generic member access RFC update is in progress, splitting type tagged downcasting into it's own RFC
Issue Triage
- Why doesn't NoneError impl Error?
- need to review the thread, but general feeling is NoneError isn't representitive of an actual error and so shouldn't exist
- added to project board to track the issue
- automatic filtering of query machinery out of backtraces
- Looks awesome, no involvement needed from PG-Error-Handling
- Essay on checked exceptions
- Nice user story, will keep monitoring but no action needed from PG-Error-Handling
