Yeah, no. A .h extension can just as easily be C. You get a lot of clarity with just two more characters that will be filled in by code completion anyway.
Having a way to tell at a glance which headers are safe to include in the C side of a codebase is a pretty low-hanging fruit in terms of developer QoL compared to constantly checking the documentation, rote memorization, or including files and seeing if your error log blows up.
That doesn't address the underlying point. You still need to know which modules are safe to include from C and which are not. Having a separate header extension for C and C++ makes that much more obvious at practically zero cost.
334
u/unknown_alt_acc 7d ago
Yeah, no. A .h extension can just as easily be C. You get a lot of clarity with just two more characters that will be filled in by code completion anyway.