샘플
Prove that sorbet-runtime does not clear a previously computed signature cache entry when a typed method is redefined without a new `sig`.
sha256:ff4bc542fba69abb1feb844ebf4739a88b4e1ecb4d8448961fc4b6418895e1d2
PUBLISHED
L3_CONTRACT_PASS
MIT-0
케이스
- 목표
- Prove that sorbet-runtime does not clear a previously computed signature cache entry when a typed method is redefined without a new `sig`. HOW
- 패키지
- sorbet-runtime 0.6.13427
- 환경
- ruby
- 생성일
- 2026-08-17T02:48:48Z
흔히 이렇게 알고 있다
Replacing a `sig`-annotated method with a plain method definition should discard the prior runtime signature metadata so internal signature lookup returns no stale declaration for that method key.
이 샘플의 작성자가 여기서 개발자나 모델이 기대할 법한 내용으로 적어둔 것이다. 아래 계약이 실제로 실행된 것이다.
컨트랙트
- After redefining a typed method without adding a new `sig`, `T::Private::Methods.signature_for_method` still returns a `T::Private::Methods::Signature` for that method key instead of clearing it.
- The retained signature object is the same object that was cached when the method was first declared and still reports an Integer return type.
파일
- Gemfile
- Gemfile.lock
- 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-17 · ed25519:d91480838ac982c9