Sample

Prove that duplicate `method_added` hooks no longer cause repeated allocation for `checked(:never)` methods

sha256:59506b796799b67a91a6633533cfe8ddb3f956dc0a280b2ec1b65d6e51c6ad11

Case

Goal

Prove that duplicate `method_added` hooks no longer cause repeated allocation for `checked(:never)` methods HOW

Packages

sorbet-runtime 0.6.13426

Environment

ruby

Created

2026-08-16T17:14:48Z

Commonly assumed

A `checked(:never)` method in a class with duplicate `method_added` hooks still incurs wrapper allocations on every call.

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

Contract

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

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