> one .c file in your project that produces all the implementations for your specialized types That depends on the compiler, linker and desired linking being

> one .c file in your project that produces all the implementations for your specialized types That depends on the compiler, linker and desired linking being static or dynamic and resource concerns. If dynamic, the entire specialized/monomorphized library could be loaded for a single function compared to static linking with the "-O2 -flto" options that removes unused functions.