Too big `string` to `int` cast results nonsense

[kkmuffme]

Description

The following code:

<?php
if ( (string) PHP_INT_MAX === '9223372036854775808' ) {
    echo "string identical" . PHP_EOL;
}

if ( PHP_INT_MAX === (int) '9223372036854775808' ) {
    echo "int identical" . PHP_EOL;
}

Resulted in this output:

int identical

But I expected this output instead:

Deprecated: Conversion from string '9223372036854775808' to int loses precision

A very similar error already exists when converting float to int implicitly e.g. $a[ PHP_INT_MAX + 1 ] = '';

See also #17081 which reports that for float/int casts

PHP Version

PHP 8.4.8

Operating System

No response

[kkmuffme]

Possibly though this could be a fatal too, similar to what there is for e.g.

echo (object) 15;

Fatal error: Uncaught Error: Object of class stdClass could not be converted to string

But in this case would be:

Fatal error: Uncaught Error: String '9223372036854775808' could not be converted to int

[iluuu1994]

Explicit casts generally do not trigger warnings. That said, I see this is also unexpected:

var_dump(PHP_INT_MAX == '9223372036854775808'); // true

The implicit string to int coercion should probably warn. As for the rest, I'd say works as intended, needs an RFC to change. /cc @Girgias

[Girgias]

That's more something that should have been targeted with @nikic's Saner string to number comparisons RFC

But I guess warning is probably reasonable, and yes the cast is "as intended" because a large float to int also just works with a cast

[bwoebi]

There should not be an implicit string to int coercion in weak equality comparison if the value is out of range in the first place. Ilijas example simply is a bug. There should not be a warning here.