hash-prospector VS scratch

But for good general purpose hash functions, you can also take a look at u/skeeto's prospector project.

Special thanks to hash-prospector for inspiration and useful information.

A project to keep an eye on in the future. The -search command is very much like my own hash search, plugging different constants into xmxmx.

Maybe look at https://github.com/skeeto/hash-prospector https://www.reedbeta.com/blog/hash-functions-for-gpu-rendering/

New best known functions

https://github.com/skeeto/hash-prospector (recently outdone)

Where each 0xXXXXXXXX is a random, odd 32-bit integer. Not all choices are equal, and you can find some excellent xmx parameters here: https://github.com/skeeto/hash-prospector/issues/19

For my stack based texture generator I used (utilizing https://github.com/skeeto/hash-prospector )

  let intHash = x => {

This is one of the best known hashes for 32 bit integers. See https://github.com/skeeto/hash-prospector and https://nullprogram.com/blog/2018/07/31/

pbmview, an image viewer (windows subsystem).

For comparison (for those following along): https://github.com/skeeto/scratch/blob/master/parsers/qoi.c https://github.com/skeeto/scratch/blob/master/parsers/ini.c

Another option I learned a couple years ago is embedding a UTF-8 manifest ([details])[https://github.com/skeeto/scratch/tree/master/libwinsane]. Also put the console in UTF-8 mode (SetConsoleOutputCP(CP_UTF8)), and you're done. Works on Windows 10 and later. This covers everything: argv is UTF-8 and fopen accepts UTF-8 paths. (This is exactly how CRTs should have worked all along.)

I was thinking more about this and I realized it's quite easy to do it in arbitrary precision, so here's my take: https://github.com/skeeto/scratch/blob/master/misc/bswap.c

As was linked from my QOI article, here's my full decoder with comments: qoi.c. Each pixel decodes to a 32-bit integer, ABGR. That corresponds to SDL's SDL_PIXELFORMAT_ABGR8888. SDL_UpdateTexture copies that data into the texture's internal storage, and font is no longer needed. (In a real program I'd allocate it in a scratch arena, reset after initialization.)

A recent, interesting experience with function+context allocation: For more than a decade, Windows accidentally exposed part of zlib in a public DLL, and (overly-)clever applications can exploit this as a "system zlib." Though it doesn't export the "end" functions, so cleanup seems impossible. However, custom allocation works, so doesn't matter. I plugged it into an arena.