Explore >> Select a destination
|
You are here 
|
npf.io | ||
| | | | |
lwn.net
|
|
| | | | | Gives some background, the current state, and potential timeline for including generics in the Go programming language (LWN.net). | |
| | | | |
kristoff.it
|
|
| | | | | Let's take a quick look at what compile-time execution looks like in Zig. | |
| | | | |
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 . | |
| | | | |
soundmacguy.wordpress.com
|
|
| | | I thought I was done with SCEP (see parts 1, 2 and 3) but whilst undertaking an exercise looking into using SCEP on some Linux servers (and specifically looking at how it can provide reporting data to SCOMvia a Management Pack), I inadvertently came across a little-documented command line argument for one of its binaries,... | ||
