I wonder tho: with flat data structures — is it better to index at 0 and use the MAX number as the terminator? Or index at 1 and use the MIN number as the terminator (e.g. 0)? 0x0000 is easy to spot which is quite nice haha.
Show this thread
Haha, yeah using TypedArrays to flat pack data structures is so much fun Instead of {a: 6, b: 7, prev: 2, next: 0} we could store it as a quad in a Uint16Array as [6,7,2,0]. Iterating over items is done in jumps of 4. Index at 1, and terminate at 0 and we have minimal GC! :D
-
-
-
Anyway, reusing sequences of bytes that have been allocated ahead of time is probably going to work out real nice for this thing I'm working on :D
Show this thread
End of conversation
New conversation -
-
-
We do { a: [6], b: [7], prev: [2], next: [0] } in perf.html to optimize away GC. Adding an entry involves pushing to each array, but then you have a stable index into that table of data.
-
We are immutable by default so changing values involved throwing away lots of data, but GC is not a perf issue anymore.
- 4 more replies
New conversation -
-
-
Y'all are reinventing writing asm-memory-handling and we have yet to invent C. Manually doing array offsets is not a nicely maintainable way of writing code :)
-
Heh, well if you only need to write it once to implement an existing algorithm it's not too bad either. Once WASM runs everywhere (and we have shared memory) we'll get C and everything that followed too!
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.