Isn't that to be expected? print_str() is called from array_map()
and the latter is not declared in a declare(strict_types=1) file.

> Isn't that to be expected? print_str() is called from array_map()
> and the latter is not declared in a declare(strict_types=1) file

shouldn't it be logical that when *all* of your files start with declare(strict_types=1) everything has to use strict typing?

Same result in:

<?php

declare(strict_types=1);

$input = [1, 2, 3];
array_map(function(string $foo) {
    var_dump($foo);
}, $input);

?>

> Isn't that to be expected? print_str() is called from array_map()
> and the latter is not declared in a declare(strict_types=1) file.

Does that mean that user defined functions are not affected by declare(strict_types=1), if they called by internal functions?


// call_user_func respect strict_types
call_user_func(function(string $foo) {
    var_dump($foo);
}, $input);

// array_filter ignores strict_types
array_filter($input, function(string $foo) {
     var_dump($foo);
});

This is not particularly related to internal functions; rather
whether strict_types apply depends on where a function is
*called*[1].  Internal functions are practically defined in non
strict_type files.

If anybody feels this behavior should be changed, please pursue
the RFC process[2].

[1] <https://www.php.net/manual/en/language.types.declarations.php#language.types.declarations.strict>
[2] <https://wiki.php.net/rfc/howto>