Files
tsl-devkit/docs/tsl/syntax/25_set_operations.md
T
csh 3d83740f88 Squashed 'docs/standards/playbook/' changes from c3f8137..25d895d
25d895d 🐛 fix(gitea_workflow): clean up temp repos after job steps
2bc3b11 🐛 fix(gitea_workflow): clean up temporary repo dirs in workflows
98c3f30 📝 docs(agent_rules): allow plan execution on current branch
16c7230 📝 docs(prompts): define custom verify layering
8efc4dd 🐛 fix(skills): quote commit-message description
bc8498f 🐛 fix(ci): install tomli for gitea tests
55cda3b 🐛 fix(tests): report missing toml parser clearly
c0729c7 🐛 fix(playbook): import Optional for cli compatibility
63e24bf 📦 deps(skills): sync thirdparty skills
d2f9356 🐛 fix(ci): isolate gitea workflow repos
588b81d 🐛 fix(ci): inline gitea workflow bootstrap
e0b1c3a ♻️ refactor(skills): standardize first-party skill contracts
2c5050d ♻️ refactor(skills): rename repo skills source dir
f049dfb 📦 deps(skills): drop duplicate first-party superpowers skills
234b335  feat(workflow): add superpowers planning and execution state tracking
c1702a6 📝 docs(markdown): format tracked markdown and drop stale templates
2325409 📝 docs(markdown): clarify optional markdownlint usage
214c44e 🔧 chore(markdown): add markdownlint baseline and lint fixes
a22b324 📝 docs(templates): add execution and memory-bank prompt templates
223a797 📝 docs(templates): update README for Claude Code and current features
4ac8672 📝 docs: simplify README + platform-agnostic tools + auto-create local rules
2431c9d 📝 docs: add claude_md config and use cross-platform paths
d64b248 📝 docs: fix README.md inaccuracies and add Claude Code info
c8d6bf2 🐛 fix(playbook): use relative paths in CLAUDE.md when not at project root
6518f0f  feat(playbook): auto-create CLAUDE.md with path discovery
6ec9a45  feat(skills): add skill_link symlink support + platform-agnostic prompt
9f8b6b5 📝 docs: update README and config example for Claude Code support
79cff6c 📝 docs(skills): add Claude Code platform support
452c6f5  feat(playbook): auto-inject AGENTS.md into CLAUDE.md
e1dbf3c 🐛 fix(skills): remove dual-path from commit-message skill
f3a7259 🔧 chore(ci): use prepare_repo.sh in both workflows
da08212 🔧 chore(ci): extract prepare_repo.sh and clean up workflows
7ade85e 🗑️ remove(tsl): drop syntax_book/, data/ source and build script
f94dba0 ♻️ refactor(skills): update playbook.py and tests for thirdparty/ layout
b3df412 ♻️ refactor(skills): separate thirdparty skills into thirdparty/ subdirectory
64950e7 📦 deps(skills): sync thirdparty skills
a2e3cb0  feat(playbook): add no_backup deploy controls
8609d59 🐛 fix(docs): repair reference catalog source links
956da11 🐛 fix(playbook): publish hidden ci test fixes
3f67754 📦 deps(skills): sync thirdparty skills
08ca87b 📦 deps(skills): add karpathy thirdparty sync
96b705b 📝 docs(tsl): rebuild canonical syntax and routing manual
3ed5052 📦 deps(skills): sync thirdparty skills
60108dd 📦 deps(skills): sync thirdparty skills
da85d4e 🐛 fix(thirdparty): prune nested project snapshots
a2a697e 📦 deps(skills): sync thirdparty skills
9df610a 🐛 fix(thirdparty): exclude duplicated superpowers skills
33dd5bb 🐛 fix(thirdparty): preserve optional manifest fields
91b0ea7 🐛 fix(thirdparty): preserve manifest during snapshot update
2e26f98 🔧 chore(thirdparty): generalize skills sync pipeline
5b9c1e3 📦 deps(skills): sync superpowers
2f2d34a 📝 docs(readme): normalize subtree command spacing
62db7db 🐛 fix(ci): serialize superpowers update and sync
3463223 🐛 fix(ci): use literal superpowers sync paths
48f6de8 📦 deps(skills): sync superpowers
4b23529 🔧 chore(ci): merge superpowers update and sync workflow
a56d75b 📦 deps(skills): sync superpowers
84bcefa 🔧 chore(ci): use ci[bot] commit author name
00a07e5 📦 deps(skills): sync superpowers
7b84daf 🐛 fix(templates): enforce main loop progress tracking
51373d7 🔧 chore(ci): automate superpowers sync workflow
eaaa39c 🐛 fix(ci): prevent stale superpowers sync from restoring skills block
79755c6 📦 deps(skills): sync superpowers
836d878 📦 deps(skills): sync superpowers
8216c9f 📦 deps(skills): sync superpowers
9439505 🐛 fix(playbook): address reported repo issues

git-subtree-dir: docs/standards/playbook
git-subtree-split: 25d895d8b3f56624ccfe99ad7289e9eb49e0f316
2026-05-24 13:04:14 +08:00

6.1 KiB

Set Operations

文档类型:语法主线 是否可直接用于生成代码:是 是否含已验证可执行示例:是 是否含已验证反例:是 遇到不确定时跳转到:14_resultset_and_filters.md13_matrix_and_collections.md12_pitfalls.md

手册位置:第 25 篇,共 32 篇。上一篇:24_builtin_runtime_objects.md。下一篇:26_matrix_deep_dive.md

这一篇只讲集合运算本身:insqlinunion2intersectminusoutersect。它和 14_resultset_and_filters.md 的分工很明确: 这一篇讲“去重后的集合关系”,过滤页讲“按原结果集逐行保留或排除”。

这一篇解决什么问题

回答“某个元素是否在数组里、某组元素是否构成子集、某一行是否存在于结果集中,以及两个结果集如何做并集、交集、差集和对称差集”。

必须记住的规则

  • in / not in 处理的是元素存在关系,以及左侧为数组时的子集关系。
  • sqlin / not sqlin 处理的是行存在关系;左侧要当成一整行去匹配右侧结果集。
  • union2intersectminusoutersect 都按“行”运算,而不是按单元格逐个运算。
  • 当前解释器支持 not innot sqlin 这种否定写法。
  • 集合运算结果会折叠重复行;如果需求是保留重复记录,不要用这一篇的算符,改看 14_resultset_and_filters.md
  • 当数据本身就是一维数组时,按行集合运算和按元素集合运算是一致的。

已验证语法

innot in

in 既可以判断单个元素是否存在,也可以判断左侧数组是否是右侧结果集的子集:

代码块身份:已验证可执行示例

program test;
begin
    WriteLn(1 in array(1, 2, 2));
    WriteLn(1 in array(0, 2));
    WriteLn(1 in array((1), (2)));
    WriteLn(array(1, 2) in array(1, 2, 3, 4));
    WriteLn(array(1, 3) in array((1, 2), (3, 4)));
    WriteLn(array(1, 2) in array(1));
    WriteLn(1 not in array(0, 2));
end.

已验证运行结果:

  • 1 in array(1, 2, 2) 输出 1
  • 1 in array(0, 2) 输出 0
  • 1 in array((1), (2)) 输出 1
  • array(1, 2) in array(1, 2, 3, 4) 输出 1
  • array(1, 3) in array((1, 2), (3, 4)) 输出 1
  • array(1, 2) in array(1) 输出 0
  • 1 not in array(0, 2) 输出 1

sqlinnot sqlin

sqlin 改成按整行判断左侧是否存在于右侧结果集中:

代码块身份:已验证可执行示例

program test;
begin
    WriteLn(1 sqlin array(1, 2));
    WriteLn(array(1, 2) sqlin array(1, 2, 3));
    WriteLn(array(1, 2) sqlin array((1, 2), (3, 4)));
    WriteLn(array(5, 6) not sqlin array((1, 2), (3, 4)));
end.

已验证运行结果:

  • 1 sqlin array(1, 2) 输出 1
  • array(1, 2) sqlin array(1, 2, 3) 输出 0
  • array(1, 2) sqlin array((1, 2), (3, 4)) 输出 1
  • array(5, 6) not sqlin array((1, 2), (3, 4)) 输出 1

可以把两者的差异直接记成一句话:

  • in 看元素或子集
  • sqlin 看整行

行集合的并、交、差、对称差

下面这组最小例子同时验证了“按行运算”和“结果会折叠重复行”:

代码块身份:已验证可执行示例

program test;
begin
    A := array((1, 2), (1, 2), (2, 3));
    B := array((1, 2), (3, 4));
    U := A union2 B;
    I := A intersect B;
    M := A minus B;
    O := A outersect B;
end.

已验证运行结果:

  • A union2 B 共有三行:(1,2)(2,3)(3,4)
  • A intersect B 只有一行:(1,2)
  • A minus B 只有一行:(2,3)
  • A outersect B 有两行:(2,3)(3,4)
  • A 原本有两行相同的 (1,2),但 union2 / intersect 的结果都只保留一份,说明集合运算会折叠重复行

如果你需要看更大的四列结果集例子,当前解释器下也已经实测过:

  • array((1,2,3,4),(2,3,4,5),(1,1,1,1)) union2 array((1,2,3,4),(3,4,5,6),(2,2,2,2)) 返回 array((1,2,3,4),(2,3,4,5),(1,1,1,1),(3,4,5,6),(2,2,2,2))
  • 同一组输入下: intersect 返回 array((1,2,3,4))
  • 同一组输入下: minus 返回 array((2,3,4,5),(1,1,1,1))
  • 同一组输入下: outersect 返回 array((2,3,4,5),(1,1,1,1),(3,4,5,6),(2,2,2,2))

和过滤运算的区别

  • 集合运算先把数据当成“行集合”来看,再做包含、并交差。
  • 过滤运算先保留“原结果集里的每一条命中记录”;因此重复行会保留下来。
  • 你要的是“集合关系”,看这一篇。
  • 你要的是“从原表里筛出哪些行”,看 14_resultset_and_filters.md

最小可编译示例

如果你只想先记住最短写法,从这里开始:

代码块身份:已验证可执行示例

Matched := 1 in array(1, 2, 3);

常见误写

  • insqlin 当成同一个概念。
  • 期待 union2 保留重复行。
  • 用集合运算去做“保留原始重复记录”的过滤任务。
  • 把二维结果集默认当成“按元素逐个比较”的集合运算。

代码块身份:反例 / 不可照写

Matched := array(1, 2) in array((1, 2), (3, 4));

上面这类写法不要直接理解成“左边这一整行是否存在于右边”。当前手册里,整行存在判断统一写成 sqlin,避免把 in 的子集语义和行匹配语义混在一起。

代码块身份:反例 / 不可照写

OnlyLeft := A minus B;

如果你的任务要求保留 A 里重复出现的命中次数,上面这种集合差集就不是合适工具,因为它会把结果当成集合而不是原始记录流。

跳转指引