You are here |
hypothesis.works | ||
| | | |
blog.metaobject.com
|
|
| | | | Now that I've motivated why an MPWObjectCache might be useful , let's go into some more detail as to how it actually works. To follow along... | |
| | | |
siderite.dev
|
|
| | | | While trying to optimize a sorting algorithm that worked on iterables I've noticed how slow iterators and generator functions are. | |
| | | |
mfbmina.dev
|
|
| | | | One of my favorite features in Go is the possibility of writing benchmark tests. At Go 1.24, this feature has a new look, making it easier to use. To demonstrate these changes, let's suppose a function that calculates the factorial recursively and one that calculates it through loops. func FatorialRecursive(n int) int { if n == 0 { return 1 } return n * FatorialRecursive(n-1) } func FatorialLoop(n int) int { aux := 1 for i := 1; i <= n; i++ { aux *= i } return aux } Previously, to write a benchmark, it was necessary to write down the whole execution loop of the test. When done, we need to run the command $ go test -bench . | |
| | | |
charity.wtf
|
|
| | Last night I was out with a dear friend who has been an engineering manager for a year now, and by two drinks in I was rattling off a long list things I alwayssay to newer engineering managers. Then I remembered: I should write a post! It's one of my goals this year to write... |