Ahh… interesting! Could you share any more details about the struct that was migrated to CowBox? What does MemoryLayout return for size (and stride)? What is the memory footprint of one struct instance?
My expectation when building the CowBox macro was engineers were focused on optimizing memory as a primary goal. A secondary goal (if a struct was copied many many times) was optimizing CPU. The honest truth is I did not think to rigorously test for binary size optimizations. I would not have expected engineers would see any kind of stat-sig reduction in binary size from migrating to CowBox… but a legit 90 percent reduction in binary size with very complex structs is awesome.
I would appreciate any more details you might have about how this struct is built and how this struct is called. It would be great if I could repro these binary size reductions in a test project. Thanks!