/explore
|
You are here 
|
phauer.com | ||
| | | | |
www.milanjovanovic.tech
|
|
| | | | | How should you handle errors in your code? This has been a topic of many discussions, and I want to share my opinion. One school of thought suggests using exceptions for flow control. This is not a good approach because it makes the code harder to reason about. The caller must know the implementation details and which exceptions to handle. Exceptions are for exceptional situations. Today, I want to show you how to implement error handling using the Result pattern. It's a functional approach to error handling, making your code more expressive. | |
| | | | |
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. | |
| | | | |
adambennett.dev
|
|
| | | | | Android Bennett's blog :: android, kotlin, thoughts, opinions, occasional rants | |
| | | | |
mcyoung.xyz
|
|
| | | [AI summary] The article provides an in-depth exploration of computer architecture and assembly language, focusing on the RISC-V Instruction Set Architecture (ISA). It covers fundamental concepts such as machine words, registers, and the role of assembly language as a human-readable representation of machine instructions. The text explains how programs are structured using instructions, labels, and directives, and categorizes instructions into arithmetic, memory, control flow, and miscellaneous types. It also delves into the calling convention, which defines how functions are called and how data is passed between them, and highlights the importance of maintaining the call stack illusion. The article further discusses the practical implications of these conce... | ||
