Errors get a bad rep just because they make it look like something is wrong, and it’s your fault. It shouldn’t be that way. Errors are normally misunderstandings between the application and whoever is interacting with it—the programmer or the final user. It’s then our responsibility to determine what the misunderstanding is, and up to a point, figure out what the application was expecting. Designing errors (we will call them errors, for the sake of brevity, when we mean misunderstandings) and the messages they deliver is a big part of getting an application or module just right. In this chapter, we focus ...
Get Raku Recipes: A Problem-Solution Approach now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
