/explore
|
You are here 
|
blog.ploeh.dk | ||
| | | | |
andreabergia.com
|
|
| | | | | Error handling is a fundamental aspect of programming. Unless you are writing hello world, you will need to handle errors in your code. In this post, I will discuss a bit the most common approaches used by various programming languages. Return error codes This is one of the most ancient strategies - if a function can fail, it can simply return an error code - often a negative number, or null. | |
| | | | |
www.foonathan.net
|
|
| | | | | This post describes techniques for libraries to allow both exceptions and non-exceptional use. One is a technique I dubbed exception handler. | |
| | | | |
patshaughnessy.net
|
|
| | | | | [AI summary] A Ruby developer explains the unique challenges of mastering Rust's mandatory error handling by comparing it to learning a foreign language with distinct vocabulary for concepts like success and failure. | |
| | | | |
blog.jcoglan.com
|
|
| | | [AI summary] This technical article explores the challenges and solutions for implementing strict named argument semantics in JavaScript, comparing approaches from Ruby and Python, and detailing how TypeScript's type system and runtime checks like Object.keys() can enforce required fields and reject unwanted options while handling prototype pollution risks. | ||
