Explore >> Select a destination
|
You are here 
|
darkcoding.net | ||
| | | | |
www.integralist.co.uk
|
|
| | | | | I found myself recently trying to recall specific details of how slices work when needing to do something that meant I wanted to not mutate the underlying array data structure of the slice I was working with. Now the reason for why I wanted to do that isn't important. What's motivating this write-up is my want for a good reference document (not saying the official go blog isn't a good reference, but I have my own things I like to focus in on in these situations). | |
| | | | |
zig.guide
|
|
| | | | | Slices can be thought of many-item pointers ([*]T) with a length (usize). | |
| | | | |
www.alexedwards.net
|
|
| | | | | ||
| | | | |
hjr265.me
|
|
| | | I know many will start with something like Gin whenever they are working on a JSON/HTTP-based backend in Go. I, not entirely sure if the minority, try to stick to Go's built-in net/http package and, at most, use Gorilla Mux in most of my Go projects. And so serving something simple like JSON is no different from the package's point of view as any other content type: whatever it is, write it out to the w, the http. | ||
