/explore
|
You are here 
|
golangbot.com | ||
| | | | |
lewisdale.dev
|
|
| | | | | Day Four brings the joys of arrays and structs | |
| | | | |
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). | |
| | | | |
divan.dev
|
|
| | | | | [AI summary] The author explains how understanding Go's internal data structure representations and memory management can help developers avoid common language gotchas like slice sharing and interface nil confusion. | |
| | | | |
coredumped.dev
|
|
| | | Updated: 2023-01-06 About a year ago I was bitten by the PL bug. It started with reading Crafting Interpreters and discovering the wonders hidden under the hood of a compiler. I am also been a big fan of Emacs, and this started to get me interested in how its interpreter works. At the same time, I was reading the Rust book and trying to understand the concepts there. This all came to a head, and I decided to write an Emacs Lisp interpreter called rune in Rust. | ||
