Explore >> Select a destination
|
You are here 
|
maskray.me | ||
| | | | |
blog.pkh.me
|
|
| | | | | It's been a very long time since I've done some actual reverse engineering work. Going through a difficult period currently, I needed to take a break from the graphics world and go back to the roots: understanding obscure or elementary tech stuff. One may argue that it was most certainly not the best way to deal with a burnout, but apparently that was what I needed at that moment. Put on your black hoodie and follow me, it's gonna be fun. The beginning and the start of the end So I started solving a few ... | |
| | | | |
mcyoung.xyz
|
|
| | | | | ||
| | | | |
blog.thea.codes
|
|
| | | | | A deep look into the black magic that is linker scripts. | |
| | | | |
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). | ||
