eserde – a serde that just doesn't stop
(github.com/mainmatter)
Don't stop at the first deserialization error.
Don't stop at the first deserialization error.
Syntax error recovery in parsing expression grammars (PEG parsers)
(arxiv.org)
Parsing Expression Grammars (PEGs) are a formalism used to describe top-down parsers with backtracking. As PEGs do not provide a good error recovery mechanism, PEG-based parsers usually do not recover from syntax errors in the input, or recover from syntax errors using ad-hoc, implementation-specific features. The lack of proper error recovery makes PEG parsers unsuitable for using with Integrated Development Environments (IDEs), which need to build syntactic trees even for incomplete, syntactically invalid programs.
Parsing Expression Grammars (PEGs) are a formalism used to describe top-down parsers with backtracking. As PEGs do not provide a good error recovery mechanism, PEG-based parsers usually do not recover from syntax errors in the input, or recover from syntax errors using ad-hoc, implementation-specific features. The lack of proper error recovery makes PEG parsers unsuitable for using with Integrated Development Environments (IDEs), which need to build syntactic trees even for incomplete, syntactically invalid programs.
Error Stacking in Rust
(greptime.com)
A detailed exploration of error handling in Rust within GreptimeDB, proposing improvements and discussing future work.
A detailed exploration of error handling in Rust within GreptimeDB, proposing improvements and discussing future work.
How we centralized and structured error handling in Golang
(olivernguyen.io)
Handling errors in Go is simple and flexible – yet no structure!
Handling errors in Go is simple and flexible – yet no structure!
Idiomatic Errors in Clojure
(daveliepmann.com)
The idiomatic Clojure approach to error-handling is that there isn’t one. There’s a whole bunch.
The idiomatic Clojure approach to error-handling is that there isn’t one. There’s a whole bunch.
Union types ('enum types') would be complicated in Go
(utoronto.ca)
Every so often, people wish that Go had enough features to build some equivalent of Rust's Result type or Option type, often so that Go programmers could have more ergonomic error handling.
Every so often, people wish that Go had enough features to build some equivalent of Rust's Result type or Option type, often so that Go programmers could have more ergonomic error handling.
Bringing Faster Exceptions to Rust
(purplesyringa.moe)
Three months ago, I wrote about why you might want to use panics for error handling.
Three months ago, I wrote about why you might want to use panics for error handling.
The Ultimate Guide to Error Handling in Python
(miguelgrinberg.com)
I often come across developers who know the mechanics of Python error handling well, yet when I review their code I find it to be far from good.
I often come across developers who know the mechanics of Python error handling well, yet when I review their code I find it to be far from good.
Rust error handling
(bitfieldconsulting.com)
Things are always going wrong, as I’m sure you’ve noticed, and that applies to our programs too. Sometimes when a function call asks a question, there’s no answer to return—either because some error happened, or because the correct answer is, simply, “no results”.
Things are always going wrong, as I’m sure you’ve noticed, and that applies to our programs too. Sometimes when a function call asks a question, there’s no answer to return—either because some error happened, or because the correct answer is, simply, “no results”.
Why I Prefer Exceptions to Error Values
(cedardb.com)
Good error handling is key to robust programs, but often dreaded by programmers because there is always one more edge case.
Good error handling is key to robust programs, but often dreaded by programmers because there is always one more edge case.