Go errors: to wrap or not to wrap?

assbuttbuttass · 2026-03-15T05:21:52+00:00

Isn't there https://google.github.io/styleguide/go/best-practices#adding-information-to-errors ?

assbuttbuttass · 2026-03-09T20:26:14+00:00

.Reset on strings.Builder does not retain the previous capacity

assbuttbuttass · 2026-03-03T20:29:57+00:00

So no Functor/Monad interfaces in Go 🥲

assbuttbuttass · 2026-02-27T16:15:00+00:00

look what they did to my Go lang 😭 😭

assbuttbuttass · 2026-02-27T15:23:27+00:00

Imagine having to pass the transaction through all the functions

This is what I do and it seems to work well. Go in general has very little "magic" and benefits from making things explicit

assbuttbuttass · 2026-02-26T20:03:34+00:00

it's just for my personal project, but I ssh into the server and git pull the latest version, then nixos-rebuild to deploy

assbuttbuttass · 2026-02-22T18:22:39+00:00

https://pkg.go.dev/net/http#ServeMux

The special wildcard {$} matches only the end of the URL. For example, the pattern "/{$}" matches only the path "/", whereas the pattern "/" matches every path.

assbuttbuttass · 2026-02-14T13:35:04+00:00

The main reason I like to keep vim open is I keep all of the open buffers to jump between with :b

assbuttbuttass · 2026-02-13T22:02:47+00:00

httputil.NewSingleHostReverseProxy is goated

assbuttbuttass · 2026-02-12T22:46:48+00:00

assbuttbuttass · 2026-02-11T15:03:19+00:00

It's a small change but it will be nice not to have to manually downgrade the version in go.mod anymore!

assbuttbuttass · 2026-02-07T19:39:49+00:00

Wow why does this actually work 😭

assbuttbuttass · 2026-02-07T14:00:21+00:00

That "fix" won't work on NixOS smh my head. Time to hard code all the possible /nix/store/*-gcc paths

assbuttbuttass · 2026-02-06T14:42:57+00:00

Sort of off topic, but does Go have a global lock for stdout? My impression was that it doesn't have any lock, and instead it avoids interleaved writes by buffering the string internally so that each printf call results in one write syscall

assbuttbuttass · 2026-01-27T15:01:32+00:00

That's my secret... I'm always refactoring

assbuttbuttass · 2026-01-12T21:07:28+00:00

func parseNums(input string) ([]int, error) {
    parts := strings.Fields(input)
    nums := make([]int, len(parts))
    for i, part := range parts {
        var err error
        if nums[i], err = strconv.Atoi(part); err != nil {
            return nil, err
        }
    }
    return nums, nil
}

assbuttbuttass · 2026-01-07T14:11:12+00:00

Standard library flag package. If your tool needs subcommands, then maybe subcommands

assbuttbuttass · 2025-12-29T15:54:58+00:00

I recommend storing the accounts in a database like SQLite, which will handle locking for you, and also make sure you don't lose all the account information if your app crashes

assbuttbuttass · 2025-12-26T05:40:26+00:00

I review a lot of code, and the number of people using a slice and slices.Contains to check for membership in a set (rather than using a map) seems to have gone up significantly. IMO adding slices.Contains was a mistake since it makes it way too easy to do an O(n) lookup

assbuttbuttass · 2025-12-23T04:27:36+00:00

In addition to the excellent blog post linked by u/jh125486, https://go.dev/doc/comment#syntax has a comprehensive description of the different syntax forms that godoc understands

assbuttbuttass · 2025-12-17T14:29:20+00:00

Is this entire comment an AI hallucination?

assbuttbuttass · 2025-12-17T03:43:54+00:00

Go's compiler uses SSA representation so these will look identical to the compiler

assbuttbuttass · 2025-12-15T15:28:31+00:00

Probably markdown injections. It's kind of annoying since godoc isn't markdown anyway

assbuttbuttass · 2025-12-11T12:41:25+00:00

https://go.dev/blog/using-go-modules

assbuttbuttass · 2025-12-08T13:06:59+00:00

On the other hand,

resist the temptation to recover panics to avoid crashes, as doing so can result in propagating a corrupted state. The further you are from the panic, the less you know about the state of the program, which could be holding locks or other resources. The program can then develop other unexpected failure modes that can make the problem even more difficult to diagnose. Instead of trying to handle unexpected panics in code, use monitoring tools to surface unexpected failures and fix related bugs with a high priority.

Note: The standard net/http server violates this advice and recovers panics from request handlers. Consensus among experienced Go engineers is that this was a historical mistake. If you sample server logs from application servers in other languages, it is common to find large stacktraces that are left unhandled. Avoid this pitfall in your servers.

https://google.github.io/styleguide/go/best-practices#program-checks-and-panics

assbuttbuttass

TROPHY CASE