Explore >> Select a destination
|
You are here 
|
cep.dev | ||
| | | | |
dave.cheney.net
|
|
| | | | | [AI summary] The author discusses updates to the errors package, focusing on automatic stack trace collection and the introduction of the %+v format verb for debugging. | |
| | | | |
changelog.com
|
|
| | | | | Mat and Carmen along with guest panelists Dave Cheney, Peter Bourgon, and Marcel van Lohuizen discuss errors in Go, including the new try proposal. Many questions get answered...What do we think about how errors work in Go? How is it different from other languages/approaches? What do/don't we like? What don't we like? Ho... | |
| | | | |
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... | |
| | | | |
kuruczgy.com
|
|
| | | [AI summary] The article explores the intersection of functional programming and logic through the lens of dependent types. It begins with foundational concepts like type constructors and inductive types, then delves into the Curry-Howard isomorphism, which links programs to mathematical proofs. The discussion covers how types represent propositions, functions as implications, and inductive types as proof strategies. Examples include defining logical relations like less than or equal to and equality, and demonstrating how to prove properties like universal quantification and mathematical identities. The article concludes with an overview of resources for further study in proof assistants like Coq and Idris, emphasizing the practical applications of dependent... | ||
