/explore
|
You are here 
|
dave.cheney.net | ||
| | | | |
grosser.it
|
|
| | | | | Why go does not have nice backtraces Collecting stacktraces is expensive, so the core language will never implement them for everything.If you need your code to be highly performant then consider making a error wrapper that can be turned on/off based on a environment variable. Simple fix import github.com/pkg/errors and use it instead of errors... | |
| | | | |
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. | |
| | | | |
alnvdl.github.io
|
|
| | | | | A bit of history, a bit of atonement, a bit of shameless self-promotion. | |
| | | | |
initialcommit.com
|
|
| | | In this article, I am going to discuss some of the key comparisons when evaluating Rust and Go. | ||
