示例
Prove that duplicate `method_added` hooks no longer cause repeated allocation for `checked(:never)` methods
sha256:59506b796799b67a91a6633533cfe8ddb3f956dc0a280b2ec1b65d6e51c6ad11
PUBLISHED
L3_CONTRACT_PASS
MIT-0
案例
- 目标
- Prove that duplicate `method_added` hooks no longer cause repeated allocation for `checked(:never)` methods HOW
- 包
- sorbet-runtime 0.6.13426
- 环境
- ruby
- 创建时间
- 2026-08-16T17:14:48Z
常见的想当然
A `checked(:never)` method in a class with duplicate `method_added` hooks still incurs wrapper allocations on every call.
这是本样本作者记下的、开发者或模型在此处通常会有的预期。下面的契约才是真正运行过的东西。
契约
- A method annotated with `sig { returns(Integer).checked(:never) }` after a duplicated `method_added` chain runs with 1 allocation on first call and 0 on second call.
- The second invocation must stay allocation-free after first successful call, proving the wrapper is not dropped by a second `_on_method_added` event.
文件
- 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