Skip to content

Commit 033ca80

Browse files
committed
blog: tighten stack deformation sentence
Session-ID: ses_39d99b9c2ffeSKxHPZAk9P7E1O
1 parent 3eef9c5 commit 033ca80

File tree

1 file changed

+4
-4
lines changed
  • www/blog/2026-02-15-k6-structured-concurrency

1 file changed

+4
-4
lines changed

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -15,10 +15,10 @@ expect to work with sync `group()` doesn't work once async gets introduced.
1515
This post is about using structured concurrency to align k6's JavaScript runtime
1616
with your expectations.
1717

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

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

0 commit comments

Comments
 (0)