75 karma · joined December 25, 2024
I sure hope it doesn't involve a bunch of shell scripts to create a new, ad hoc, informally-specified, bug-ridden...
Scaling is a sidenote, that it becomes easy is a result of hoisting everything else onto one control plane and a set of coherent APIs.
/it does like this/
Tested a bunch and this is the one I stuck with, at least until I make my own. Once the entries are all right, I use the dare I say industry standard to switch between them:
By default, telemetry data is kept only on the local computer, but users may opt in to uploading an approved subset of telemetry data to https://telemetry.go.dev.
To opt in to uploading telemetry data to the Go team, run:
go telemetry on
To completely disable telemetry, including local collection, run: go telemetry off
https://go.dev/doc/telemetryHow? Unassigned
foo := myFunc() # [...] assignment mismatch: 1 variable but myFunc returns 2 values
Assigned, but not used foo, bar := myFunc()
fmt.Println(foo) # [...] declared and not used: bar
Intentionally ignored foo, _ := myFunc()
Ignoring is a deliberate decision and trivial to review, lint and grep for.Except for, I suppose, shadowing a variable before checking it
foo, bar := myFunc()
_, bar = myFunc()
fmt.Println(foo, bar)
Which is more of a general grievance of quite some people, but I don't think that has much to do with multiple returns - and you definitely have to look at the error to pave over it afterwards.https://www.wolframalpha.com/input?i=%2810cm+sphere+of+gold+...
After charging it once with a decent balance though, I got away (almost) entirely without cash using it in combination with a virtual credit card via NFC, save for street food carts and Gachapon machines.