Skip to content

Commit 3eef9c5

Browse files
committed
blog: rename next tick to future tick
Use "future tick" language consistently in the diagram and bridge paragraph. Session-ID: ses_39d99b9c2ffeSKxHPZAk9P7E1O
1 parent 9e31cf5 commit 3eef9c5

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

www/blog/2026-02-15-k6-structured-concurrency/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ with your expectations.
1717

1818
The diagram at the top shows what goes wrong. Async doesn't just add time, it
1919
deforms your call stack. Some code runs on the stack you are in now, and some
20-
code runs on a new stack on the next tick. When that happens, the "current" tags
20+
code runs on a new stack on a future tick. When that happens, the "current" tags
2121
are different, because `group()` has already unwound and restored them.
2222

2323
## Why `group()` can't fix this on its own

www/blog/2026-02-15-k6-structured-concurrency/k6-structured-concurrency.svg

Lines changed: 4 additions & 4 deletions
Loading

0 commit comments

Comments
 (0)