Explore >> Select a destination
|
You are here 
|
machiel.me | ||
| | | | |
hermanschaaf.com
|
|
| | | | | Benchmarks of various approaches | |
| | | | |
kel.bz
|
|
| | | | | It's well known that string comparisons can leak timing information. Go is no different but exploitation is tricky. | |
| | | | |
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 . | |
| | | | |
blog.skylight.io
|
|
| | | One of the coolest features of Rust is how it automatically manages resources for you, while still guaranteeing both safety (no segfaults) and high performance. Because Rust is a different kind of programming language, it might be difficult to understand what I mean, so let me be perfectly clear: * In | ||
