Beispiel
Show that `sig(:final)` is not automatically enforced across module/class boundaries unless final checks are explicitly enabled for hooks.
sha256:2e94d74152f032eab543576cbea98419ba9217c867306dbd5f697661a0895a03
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Fall
- Ziel
- Show that `sig(:final)` is not automatically enforced across module/class boundaries unless final checks are explicitly enabled for hooks. HOW
- Pakete
- sorbet-runtime 0.6.13427
- Umgebung
- ruby
- Erstellt
- 2026-08-17T02:48:33Z
Häufige Annahme
A method marked with `sig(:final)` is always rejected when a class overrides it through include.
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
- Overriding a `sig(:final)` method by defining the same instance method in a class after including a module with that final method succeeds while final checks are not enabled.
- Enabling final checks on hooks converts the same pattern into a class-definition-time failure when a class includes a final method module and then defines that method.
Dateien
- Gemfile
- Gemfile.lock
- 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-17 · ed25519:d91480838ac982c9