()
| 46 | * canonicalization on a DIFFERENT engine — reachable because a canonical |
| 47 | * handler runs arbitrary caller code — consumes stride boundaries while the |
| 48 | * engine being checked at that moment has no frame armed. The check is then |
| 49 | * a no-op and the engine that DOES have a budget waits up to another full |
| 50 | * stride, so the residual overrun is not the one stride the walk claims. |
| 51 | * A frame is created per `withTimeLimit` span, so per-frame ticking makes |
| 52 | * that bound exact, at the cost of one property access. |
| 53 | */ |
no outgoing calls
no test coverage detected