naloveyuki/BitLogger
1
0
Fork 0
mirror of https://github.com/Nanaloveyuki/BitLogger.git synced 2026-07-26 09:52:31 +00:00
Code Issues Packages Projects Releases Wiki Activity

📝 clarify async runtime snapshots

Browse Source
This commit is contained in:
Nanaloveyuki
2026-06-14 00:38:07 +08:00
parent 2845076b27
commit d950f11b40
4 changed files with 28 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/api/async-runtime-mode.md
+8 -4
View File
@@ -2,8 +2,8 @@
name: async-runtime-mode
group: api
category: async
update-time: 20260512
description: Read the current async runtime mode and distinguish native worker behavior from compatibility behavior.
update-time: 20260614
description: Read the current async runtime mode and distinguish native-worker behavior from compatibility behavior using the same mode contract exposed through async runtime snapshots.
key-word:
- async
- runtime
@@ -37,6 +37,8 @@ Detailed rules explaining key parameters and behaviors
- `NativeWorker` is the expected mode on native-style backends, while `Compatibility` is the expected mode on targets without native background-worker semantics.
- `async_runtime_mode_label(...)` converts the enum into a stable string value.
- `async_runtime_supports_background_worker()` is a narrower boolean probe built on the same idea.
- `async_runtime_state()` packages this mode together with the current background-worker capability into one `AsyncRuntimeState` snapshot.
- In the current backend implementations, `NativeWorker` pairs with `background_worker=true` and `Compatibility` pairs with `background_worker=false`.
- This API is intentionally small and useful for lightweight branching.
- The mode result describes runtime behavior only; it should not be read as proof that every backend has been equally re-verified in the current release cycle.
@@ -78,6 +80,8 @@ e.g.:
2. Use `async_runtime_state()` when you also want worker support packaged into one object.
3. This mode distinction is about runtime behavior, not whether `src-async` itself is expected to compile for the target.
3. Use `async_runtime_mode_label(...)` when the result should leave enum space and become stable text such as `native_worker` or `compatibility`.
4. See [target-verification.md](./target-verification.md) for the current verification status of individual targets.
4. This mode distinction is about runtime behavior, not whether `src-async` itself is expected to compile for the target.
5. See [target-verification.md](./target-verification.md) for the current verification status of individual targets.