fix(telegram): avoid reply fence spread allocation · openclaw/openclaw@a2d6795
steipete
·
2026-05-18
·
via Recent Commits to openclaw:main
| Original file line number | Diff line number | Diff line change |
|---|
@@ -133,7 +133,7 @@ function supersedeTelegramReplyFenceState(key: string): boolean {
|
133 | 133 | function supersedeTelegramNonInterruptingReplyFenceChildren(key: string): boolean { |
134 | 134 | let superseded = false; |
135 | 135 | const childPrefix = buildTelegramNonInterruptingReplyFenceKeyPrefix(key); |
136 | | -for (const childKey of [...telegramReplyFenceByKey.keys()]) { |
| 136 | +for (const childKey of telegramReplyFenceByKey.keys()) { |
137 | 137 | if (childKey.startsWith(childPrefix)) { |
138 | 138 | superseded = supersedeTelegramReplyFenceState(childKey) || superseded; |
139 | 139 | } |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理,仅供阅读参考。 原文来自 — 版权归原作者所有。