Currently we don't explicitly describe how return types should be formatted. Such formatting can be enforced by SlevomatCodingStandard.TypeHints.ReturnTypeHintSpacing.
If we adopted this change, the Drupal Project would benefit by having consistency.
Provide all proposed changes to the Drupal Coding standards → . Give a link to each section that will be changed, and show the current text and proposed text as in the following layout:
Beginning with Drupal 9, parameter and return type hints should be used wherever possible. Example function definition using parameter and return type hints:
public function myMethod(MyClass $myClass, string $id): array { // Method code here. }
Beginning with Drupal 9, parameter and return type hints should be used wherever possible. Example function definition using parameter and return type hints:
public function myMethod(MyClass $myClass, string $id): array { // Method code here. }There should be no space between the closing parentheses and the colon, and one space after the colon before the return type.
For a full explanation of these steps see the Coding Standards project page →
Active
Coding Standards
This was made worse by the conversion to OOP hooks. It seems that any hook implementation that had a return type before now has a space before the colon.
Since this is only adding text that explains the example I think we can skip to step 7.