memHack refers to the strategy of storing a user's
Memory object in
global to skip the
JSON.parse() normally required at first-access of
Memory in a tick.
Normally, the way
Memory works is when first accessed in a tick all of
Memory is run though a
JSON.parse() for the tick it is being used, then after any changes have been made end-of-tick it is run though
JSON.stringify() for storage for the next tick it is accessed. The user running their code pays for this parsing/stringifying with CPU the larger the
Memory object the more costly it is to process.
So, memHack works by creating an object to store
Memory in global when global is 'first created' (and needs to be rebuilt if global dies due to code push, global reset, ect), then at the start of a tick (start of a user's main loop) deletes the 'normal'
Memory object and replaces it with the global version which due to global persisting between ticks does not need to be parsed. It finally sets the
RawMemory._parsed to the current global memHack obj, this insures changes are updated to the normal
Memory object, so that in the event of a global reset when reconstructing the
Memory object will still have the changes and that the Memory watcher / console changing still work. It is important to note, that
RawMemory._parsed is not officially documented in the API however it has been around and accessible for several years. It is possible for this method to become defunct in the future.
There are a few places you can view examples of this code: