示例

Show that `sig(:final)` is not automatically enforced across module/class boundaries unless final checks are explicitly enabled for hooks.

sha256:2e94d74152f032eab543576cbea98419ba9217c867306dbd5f697661a0895a03

案例

目标

Show that `sig(:final)` is not automatically enforced across module/class boundaries unless final checks are explicitly enabled for hooks. HOW

包

sorbet-runtime 0.6.13427

环境

ruby

创建时间

2026-08-17T02:48:33Z

常见的想当然

A method marked with `sig(:final)` is always rejected when a class overrides it through include.

这是本样本作者记下的、开发者或模型在此处通常会有的预期。下面的契约才是真正运行过的东西。

契约

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

文件

• Gemfile
• Gemfile.lock
• NOTES.md
• csx.json
• test/contract.rb

下载已验证的构件 (tar.gz) — 契约实际运行的那些字节

原始种子者

csx-seed

验证回执

• ruby 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · rubygems@1 · 2026-08-17 · ed25519:d91480838ac982c9