On 02.09.2025 10:42, Mykola Kvach wrote: > Since the current codebase already uses this approach in multiple places, > contributors may get mixed signals when similar patterns are sometimes > accepted and sometimes discouraged. Clearer project-wide guidance, or even > small clarifications in coding style, would make it easier for contributors > to align with maintainers’ expectations. > > I will adjust my patch accordingly and use has_include as you suggested.
One other thing to mention: I know time is somewhat tight, but you shouldn't be too quick either - another maintainer may have a different view, after all. Jan
