[Judah]
	Put any questions for me in here!
	
[Jesse]
	05.22.25 Judah
		Instead of going with a separate 'arch' module, I
		think we can roll that into the future 'platform'
		module instead. There's enough overlap that I
		think it makes sense. Let me know what you think,
		thanks!
	05.23.25 Judah
		I went ahead and created the platform module and
		added arch-specific extension checking. Sadly
		these happen at runtime because we're manually
		checking isa extension flags. It's probably worth
		it to add a 'SIMD' constant that we set for
		targets that will almost always support SIMD
		instructions; unsure for now.
	05.31.25 Jesse
		platform/arch merge sounds good, we can keep that going. No thoughts so far on that.
		The caching is a good idea, I wonder if we should make them enum_flags.
		I don't know if it will go over a u64 though.
	08.21.25 Judah
		I'm going to do a pretty big reorg of the repo. I'll be working in a separate branch for the time being so it shouldn't have an effect on you. When I merge this back into master I'll move your changes/modules over to the new structure.
		
		General reasoning is that I'm not happy with how I've organized everything. I went a little too Odin-like with the modules which makes them annoying to use in projects:
			- What does it mean to import meta vs meta/foo?
			- WITH_SUBMODULES works but relies on a half-baked jai feature
			- modules are tangled in such a way that making a change in one could break N
			
		How I'm fixing this:
			- base module (jc) imports most things you'd always want (memory allocation, strings, arrays, hash tables, macros, etc.)
			- x, ext, and math stay the same
			- other freestanding modules (say: encoding, math) are expected to be imported directly. None of this math/linalg or encoding/json nonsense