Explore >> Select a destination
|
You are here 
|
blog.molecular-matters.com | ||
| | | | |
austinmorlan.com
|
|
| | | | | While programming you often need some memory to do something but you dont know at compile-time how much you need. Instead you have to use malloc from C or new from C++ (or more commonly std::vector) to request a certain amount of memory to be allocated for you on the heap. Thats just how it works. You might not question this sort of pattern while doing normal programming but once you start getting into game development youll quickly learn these sorts of dynamic memory allocations that occur at runtime ca... | |
| | | | |
3zanders.co.uk
|
|
| | | | | How to write your very own SLAB memory allocator! | |
| | | | |
blog.lexfo.fr
|
|
| | | | | ||
| | | | |
www.ardanlabs.com
|
|
| | | This article was written for and published by Gopher Academy I was looking at a code sample that showed a recursive function in Go and the writer was very quick to state how Go does not optimize for recursion, even if tail calls are explicit. I had no idea what a tail call was and I really wanted to understand what he meant by Go was not optimized for recursion. I didn't know recursion could be optimized. | ||
