샘플
Prove that mutating a shared `Set` during active iteration is rejected, including repeated calls launched before the iterator finishes.
sha256:1a1097583f6c75ee4125a9ecc435d4ce7b216229f203a390b852c6aaa024b001
PUBLISHED
L3_CONTRACT_PASS
MIT-0
케이스
- 목표
- Prove that mutating a shared `Set` during active iteration is rejected, including repeated calls launched before the iterator finishes. HOW
- 패키지
- set 1.1.1
- 환경
- ruby
- 생성일
- 2026-08-16T16:52:54Z
흔히 이렇게 알고 있다
A developer can mutate a `Set` from another task or nested call while iterating it and still get a consistent final result.
이 샘플의 작성자가 여기서 개발자나 모델이 기대할 법한 내용으로 적어둔 것이다. 아래 계약이 실제로 실행된 것이다.
컨트랙트
- Mutating the shared `Set` from another thread while `each` is running must raise `RuntimeError` with `can't add a new key into hash during iteration`.
- Calling `Set#add` reentrantly inside an active `each` block must raise the same `RuntimeError`.
- Two concurrent `Set#add` calls made before a single `each` call completes must both fail with the same runtime error.
파일
- Gemfile
- NOTES.md
- csx.json
- test/contract.rb
검증된 아티팩트 내려받기 (tar.gz) — 컨트랙트가 실제로 실행된 바로 그 바이트
오리진 시더
검증 영수증
- ruby 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · rubygems@1 · 2026-08-16 · ed25519:d91480838ac982c9