Beispiel
Prove that duplicate `method_added` hooks no longer cause repeated allocation for `checked(:never)` methods
sha256:59506b796799b67a91a6633533cfe8ddb3f956dc0a280b2ec1b65d6e51c6ad11
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Fall
- Ziel
- Prove that duplicate `method_added` hooks no longer cause repeated allocation for `checked(:never)` methods HOW
- Pakete
- sorbet-runtime 0.6.13426
- Umgebung
- ruby
- Erstellt
- 2026-08-16T17:14:48Z
Häufige Annahme
A `checked(:never)` method in a class with duplicate `method_added` hooks still incurs wrapper allocations on every call.
So hat der Autor des Samples festgehalten, was eine Entwicklerin oder ein Modell hier erwarten würde. Der Vertrag darunter ist das, was tatsächlich lief.
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.
Dateien
- Gemfile
- NOTES.md
- csx.json
- test/contract.rb
Verifiziertes Artefakt herunterladen (tar.gz) — genau die Bytes, gegen die der Contract lief
Ursprungs-Seeder
Verifizierungsbelege
- ruby 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · rubygems@1 · 2026-08-16 · ed25519:d91480838ac982c9