ArrayFillSharesObject
warning native off by defaultGroup: Probable bugs
Filling an array with one object places the same object in every entry. Construct separate objects when entries must hold independent state. This inspection is disabled by default because the intended policy or use can vary.
Example
php
<?php
$a=array_fill(0,3,new stdClass()); $a[0]->id=1; echo $a[1]->id;Reported:
- line 2: Construct a separate object for each array entry.
Detection
- A resolved array_fill call uses a newly constructed object as value and constant count greater than one; a property write through one literal array index is followed by a read of that property through a different in-range index.
- Resolve builtin functions, classes, constants and methods; user-defined lookalikes are excluded. Follow only bounded local proof in one lexical scope.
- Emit one finding per violating operation, not per supporting evidence statement. When the proof is inconclusive, nothing is reported.
Exceptions (no report)
- Do not report unresolved or shadowed builtin names, unknown values, or incomplete receiver/type provenance. Unknown calls, aliases escaping, and intervening writes invalidate local proof. Similar code outside the stated detection contract is not a finding.
- Both standard suppression forms suppress this native ID.
Fix
None. Choosing a repair requires intent or additional runtime information.
PHP versions
Available throughout supported PHP 5.3–8.5 where the referenced builtin/extension is available. Respect syntax/version-specific receiver contracts; unavailable APIs are not this rule’s concern.
Configure
In custos.json:
json
{
"rules": {
"ArrayFillSharesObject": {
"enabled": true
}
}
}Suppress
Before the statement or declaration (or the first statement of the file):
php
// @custos-ignore ArrayFillSharesObject