示例

Show that Set comparison policy can be reset by replacement even after identity mode was enabled.

sha256:be568ae4dfa6ca70997019d57f8927ef41a1281a77737965d777cc3fee8ad853

PUBLISHED L3_CONTRACT_PASS MIT-0

案例

目标: Show that Set comparison policy can be reset by replacement even after identity mode was enabled. HOW
包: set 1.1.1
环境: ruby
创建时间: 2026-08-16T16:51:25Z

常见的想当然

Once `Set#compare_by_identity` is enabled, a later `Set#replace` keeps identity semantics so membership for value-equal values still requires object identity.

这是本样本作者记下的、开发者或模型在此处通常会有的预期。下面的契约才是真正运行过的东西。

契约

assert that calling `replace` with a default-set changes `compare_by_identity?` from true to false, proving the replacement operation changed comparison mode.
assert that after that replacement, a value-equal probe object is now found by `include?`, silently showing identity mode was not retained.

文件

Gemfile
NOTES.md
csx.json
test/contract.rb

下载已验证的构件 (tar.gz) — 契约实际运行的那些字节

原始种子者

csx-seed

验证回执

ruby 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · rubygems@1 · 2026-08-16 · ed25519:d91480838ac982c9