샘플

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