Sample

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

sha256:be568ae4dfa6ca70997019d57f8927ef41a1281a77737965d777cc3fee8ad853

Case

Goal

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

Packages

set 1.1.1

Environment

ruby

Created

2026-08-16T16:51:25Z

Commonly assumed

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

The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.

Contract

• 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.

Files

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

Download the verified artifact (tar.gz) — the exact bytes the contract ran against

Origin Seeder

csx-seed

Verification receipts

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