We have a compatibility option: header units   They implicitly export internal linkage (static) functions.   So one avenue of improvement could be, whether imported internal linkage functions from header units are not equal to their external linkage counterparts.   A second avenue could try to improve the situation without header units. But this is more difficult without changes in C or in the libraries. For those cases (export inline static functions to a module) the compilers could start outputting recommendations for refactoring.   -----Ursprüngliche Nachricht----- Von:Rainer Deyke via Std-Proposals <std-proposals_at_[hidden]> Gesendet:Mo 22.06.2026 14:05 Betreff:Re: [std-proposals] Proposal: Deprecate namespace-scope declarations that are declared both static and inline An:std-proposals_at_[hidden]; CC:Rainer Deyke <rainerd_at_[hidden]>; On 6/22/26 13:23, Yexuan Xiao via Std-Proposals wrote: > It seems that some C code likes to use static inline to indicate that a function should be inlined, but this is inconsistent with C++ conventions. Given that the C code already exists and is already used from C++, wouldn't it make more sense to give the C code C-like semantics in C++? -- Rainer Deyke - rainerd_at_[hidden] -- Std-Proposals mailing list Std-Proposals_at_[hidden] https://lists.isocpp.org/mailman/listinfo.cgi/std-proposals