If this is a false-positive, you can also ignore this issue in your code via the ignore-unused annotation
37
public function process_vm_readv(int $pid, CData $local_iov_addr, int $liovcnt, CData $remote_iov_addr, int $riovcnt, /** @scrutinizer ignore-unused */ int $flags): int {}
This check looks for parameters that have been defined for a function or method, but which
are not used in the method body.
If this is a false-positive, you can also ignore this issue in your code via the ignore-unused annotation
37
public function process_vm_readv(/** @scrutinizer ignore-unused */ int $pid, CData $local_iov_addr, int $liovcnt, CData $remote_iov_addr, int $riovcnt, int $flags): int {}
This check looks for parameters that have been defined for a function or method, but which
are not used in the method body.
If this is a false-positive, you can also ignore this issue in your code via the ignore-unused annotation
37
public function process_vm_readv(int $pid, CData $local_iov_addr, int $liovcnt, /** @scrutinizer ignore-unused */ CData $remote_iov_addr, int $riovcnt, int $flags): int {}
This check looks for parameters that have been defined for a function or method, but which
are not used in the method body.
In this branch, the function will implicitly return null which is incompatible with the type-hinted return integer. Consider adding a return statement or allowing null as return value.
For hinted functions/methods where all return statements with the correct type are only reachable via conditions, ?null? gets implicitly returned which may be incompatible with the hinted type.
Let?s take a look at an example:
interfaceReturnsInt{publicfunctionreturnsIntHinted():int;}classMyClassimplementsReturnsInt{publicfunctionreturnsIntHinted():int{if(foo()){return123;}// here: null is implicitly returned}}
If this is a false-positive, you can also ignore this issue in your code via the ignore-unused annotation
37
public function process_vm_readv(int $pid, /** @scrutinizer ignore-unused */ CData $local_iov_addr, int $liovcnt, CData $remote_iov_addr, int $riovcnt, int $flags): int {}
This check looks for parameters that have been defined for a function or method, but which
are not used in the method body.
If this is a false-positive, you can also ignore this issue in your code via the ignore-unused annotation
37
public function process_vm_readv(int $pid, CData $local_iov_addr, int $liovcnt, CData $remote_iov_addr, /** @scrutinizer ignore-unused */ int $riovcnt, int $flags): int {}
This check looks for parameters that have been defined for a function or method, but which
are not used in the method body.
If this is a false-positive, you can also ignore this issue in your code via the ignore-unused annotation
37
public function process_vm_readv(int $pid, CData $local_iov_addr, /** @scrutinizer ignore-unused */ int $liovcnt, CData $remote_iov_addr, int $riovcnt, int $flags): int {}
This check looks for parameters that have been defined for a function or method, but which
are not used in the method body.
Loading history...
38
}
39
40
class errno_ffi extends \FFI
41
{
42
/** @var int|CInteger */
43
public int $errno;
44
}
45
46
class execvp_ffi extends \FFI
47
{
48
public function execvp(string $file, CData $argv): int {}
In this branch, the function will implicitly return null which is incompatible with the type-hinted return integer. Consider adding a return statement or allowing null as return value.
For hinted functions/methods where all return statements with the correct type are only reachable via conditions, ?null? gets implicitly returned which may be incompatible with the hinted type.
Let?s take a look at an example:
interfaceReturnsInt{publicfunctionreturnsIntHinted():int;}classMyClassimplementsReturnsInt{publicfunctionreturnsIntHinted():int{if(foo()){return123;}// here: null is implicitly returned}}
In this branch, the function will implicitly return null which is incompatible with the type-hinted return integer. Consider adding a return statement or allowing null as return value.
For hinted functions/methods where all return statements with the correct type are only reachable via conditions, ?null? gets implicitly returned which may be incompatible with the hinted type.
Let?s take a look at an example:
interfaceReturnsInt{publicfunctionreturnsIntHinted():int;}classMyClassimplementsReturnsInt{publicfunctionreturnsIntHinted():int{if(foo()){return123;}// here: null is implicitly returned}}
In this branch, the function will implicitly return null which is incompatible with the type-hinted return integer. Consider adding a return statement or allowing null as return value.
For hinted functions/methods where all return statements with the correct type are only reachable via conditions, ?null? gets implicitly returned which may be incompatible with the hinted type.
Let?s take a look at an example:
interfaceReturnsInt{publicfunctionreturnsIntHinted():int;}classMyClassimplementsReturnsInt{publicfunctionreturnsIntHinted():int{if(foo()){return123;}// here: null is implicitly returned}}
Loading history...
66
public function read(int $fd, CData $buffer, int $size): int {}
In this branch, the function will implicitly return null which is incompatible with the type-hinted return integer. Consider adding a return statement or allowing null as return value.
For hinted functions/methods where all return statements with the correct type are only reachable via conditions, ?null? gets implicitly returned which may be incompatible with the hinted type.
Let?s take a look at an example:
interfaceReturnsInt{publicfunctionreturnsIntHinted():int;}classMyClassimplementsReturnsInt{publicfunctionreturnsIntHinted():int{if(foo()){return123;}// here: null is implicitly returned}}
sj-i /
php-profiler
Loading history...
This check looks for parameters that have been defined for a function or method, but which are not used in the method body.