mbstring: Do functions marked “TODO Return void” require an RFC to change return type?

Hi,

In ext/mbstring/php_mbregex.c, I noticed several places with comments like:

// TODO Return void
RETURN_TRUE;

ext/mbstring/php_mbregex.c:1567

This suggests the intent is to change these functions to return void instead of bool.

Before preparing a patch, I wanted to confirm the process:

Would changing these functions from returning true to void (i.e., RETURN_NULL() in C and updating stubs to: void) require an RFC?
Or is this considered a minor/internal API cleanup that can go directly as a PR?

I’m aware that this could have a userland impact if the return value is currently used, so I wanted to check what the preferred approach is.

Happy to prepare a PR once the direction is clarified.

Thanks!

Commencez par ext/mbstring/php_mbregex.c:1567 et examinez les commentaires TODO environnants ainsi que les stubs de fonction associés mentionnés dans l’issue. Déterminez si la modification du type de retour affecte l’API userland et nécessite un RFC ; l’issue est terminée lorsque le processus et le périmètre du projet sont confirmés avant de préparer un patch.