A Fiber moves through not-started, running, suspended and terminated states, with errors propagated to its resumer.
The examples below begin with the core behavior, then move to an application-oriented use.
How PHP Fiber: Lifecycle and Error Handling Works
A Fiber moves through not-started, running, suspended and terminated states, with errors propagated to its resumer.
Example 1: Basic Usage
This example uses a small input to make the main behavior visible.
<?php
$fiber = new Fiber(fn() => Fiber::suspend("paused"));
var_dump($fiber->isStarted());
$fiber->start();
var_dump($fiber->isSuspended());
Output:
bool(false)
bool(true)
A Fiber moves through not-started, running, suspended and terminated states, with errors propagated to its resumer.
Example 2: A Different Input
A different set of values shows the same operation in another situation.
<?php
$fiber = new Fiber(function (): void { try { Fiber::suspend("ready"); } catch (LogicException $error) { echo $error->getMessage(); } });
$fiber->start();
$fiber->throw(new LogicException("canceled"));
Output:
canceled
Calling resume() in the wrong state raises an exception; a Fiber that throws is terminated.
Practical Example: Applying the Feature
This example shows an application-style use of the feature, with its surrounding setup visible.
<?php
$fiber = new Fiber(function (): void { try { Fiber::suspend("paused"); } finally { echo "cleaned"; } });
$fiber->start();
$fiber->resume();
Output:
cleaned
The code is shown for learning. Adjust the class names, inputs and error handling to suit your application.
Important Behavior and Edge Cases
- Calling resume() in the wrong state raises an exception; a Fiber that throws is terminated.
- A Fiber moves through not-started, running, suspended and terminated states, with errors propagated to its resumer.
- Observe differences in empty inputs, invalid states and optional extension availability where relevant.
Comparison With Related Approaches
| Approach | Important Difference |
|---|---|
PHP Fiber: Lifecycle and Error Handling | A Fiber moves through not-started, running, suspended and terminated states, with errors propagated to its resumer. |
| Alternative approach | Generators offer simpler lazy sequences when a whole call stack does not need suspension. |
Common Beginner Mistakes
| Mistake | Correct Approach |
|---|---|
Ignoring the documented state or precondition of PHP Fiber: Lifecycle and Error Handling | Calling resume() in the wrong state raises an exception; a Fiber that throws is terminated. |
| Expecting a different type of result | Read the declared return type and distinguish returned values from changes to the source object. |
| Assuming a related API works identically | Generators offer simpler lazy sequences when a whole call stack does not need suspension. |
Key Takeaways
- A Fiber moves through not-started, running, suspended and terminated states, with errors propagated to its resumer.
- Calling resume() in the wrong state raises an exception; a Fiber that throws is terminated.
- Use the example that matches the values, runtime version and dependencies in your application.
PHP Fiber: Lifecycle and Error Handling is useful when its behavior matches the data structure and lifecycle of your PHP application. Choose it with a clear understanding of its preconditions and returned values.