Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.php.net/manual/ and the instructions on how to report
a bug at http://bugs.php.net/how-to-report.php

It would only fail if you use strict_types. You can find more info on http://php.net/manual/en/functions.arguments.php#functions.arguments.type-declaration.strict

Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.php.net/manual/ and the instructions on how to report
a bug at http://bugs.php.net/how-to-report.php

http://php.net/manual/en/functions.returning-values.php#functions.returning-values.type-declaration

"Strict typing also has an effect on return type declarations. In the default weak mode, returned values will be coerced to the correct type if they are not already of that type. In strong mode, the returned value must be of the correct type, otherwise a TypeError will be thrown."

Either way you don't get the integer 1.

bleh

it's one thing taht you dont't understand strict typing but what you repoted is simly not true and WHERE is the execution part of your snippet?

[harry@srv-rhsoft:/downloads]$ cat test.php
<?php
class A{
 static public function r():bool{
  return 'ww';
 }
}

var_dump(A::r());
?>

[harry@srv-rhsoft:/downloads]$ php test.php
bool(true)

OP likely originally used print_r, which shows true as "1" and false as "", then changed the code to var_dump.

Last comment by spam2 at rhsoft dot net deleted, due to use of unnecessarily antagonistic language without contributing any valuable insight for this bug report.

Please refrain from such comments in the future.