24620719379
13%

Ran 19 Apr 2026 04:14AM UTC

Jobs 1

Files 370

Run time 1min

Badge

Embed ▾

Committed 19 Apr 2026 04:13AM UTC coverage: 1.953%. Remained the same

Build # 24620719379

Build Type

push

github

Committed by

MagicalTux

Commit Message

ROADMAP: correct the claim about object ID tracking

Goro does implement PHP-style refcounting (ZObject.refCount in
core/phpobj/zobject.go, IncRef/DecRef throughout) and does recycle
object IDs via a free list (NextObjectID/ReleaseObjectID in
core/phpctx/global.go). Destructors fire synchronously when refcount
hits zero, not when the Go GC happens to run. The previous wording
blamed the Go tracing GC for object-id drift, which is backwards.

The real edge cases are much narrower: Go function-argument
temporaries stay alive until the enclosing Go statement ends, which
causes a few ext/gmp tests to see object IDs shifted by one. Plus
goto (unimplemented), debug_zval_dump refcount format, RNG parity,
and SensitiveParameter redaction.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Coverage Stats

2185 of 111881 relevant lines covered (1.95%)

70.41 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	24620719379.1	19 Apr 2026 04:14AM UTC	370	1.95	GitHub Action Run

KarpelesLab / goro / 24620719379
13%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 24620719379

KarpelesLab / goro / 24620719379 13%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 24620719379

KarpelesLab / goro / 24620719379
13%

README BADGES
x