Exemplo

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

sha256:be568ae4dfa6ca70997019d57f8927ef41a1281a77737965d777cc3fee8ad853

Caso

Objetivo

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

Pacotes

set 1.1.1

Ambiente

ruby

Criado

2026-08-16T16:51:25Z

O que costuma-se supor

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

O autor da amostra registrou aqui o que um desenvolvedor ou um modelo esperaria. O contrato abaixo é o que de fato rodou.

Contrato

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

Arquivos

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

Baixar o artefato verificado (tar.gz) — exatamente os bytes contra os quais o contrato rodou

Seeder de origem

csx-seed

Recibos de verificação

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