Discussion

@navi @SRAZKVT i'm using automake now and it's unfortunately very comfy and allows me to not build a whole build system before writing some got damn c code. hoping that getting more familiar with this (and maybe doing automake extensions, it's written in perl) will be a good stepping stone towards a Good Build Tool for C

@navi @hipsterelectron to me interface headers are the ones who should be written by hand, this way you could have a tool that checks if there is any function that isn't marked as static that also isn't in header, and gets flagged, and then, either it's forgotten from header, so you know to add it, or it should be static, and you fix it

not many people check generated files, so while you COULD check it, nearly nobody would

@navi @hipsterelectron to me interface headers are the ones who should be written by hand, this way you could have a tool that checks if there is any function that isn't marked as static that also isn't in header, and gets flagged, and then, either it's forgotten from header, so you know to add it, or it should be static, and you fix it

not many people check generated files, so while you COULD check it, nearly nobody would

@hipsterelectron @SRAZKVT sure modules introduced in C++20 are already implemented in the most popular compilers right? RIGHT?
Hahahaha (dies)

@SRAZKVT the point i was making with rust is that it employs an implementation technique that could be used to solve exactly this problem. what you've identified here is imo an interface issue and not an implementation problem—it's a problem because of how the interface fails to model the appropriate program structure, and we can solve it by cheating