rigor-sorbet

Lets Rigor read an existing Sorbet codebase as a type source: inline sig { ... } blocks, RBI files, and the T.let / T.cast / T.must / T.unsafe / T.bind / T.assert_type! / T.absurd assertion forms are translated into Rigor’s own carriers, so you can run rigor check alongside srb tc without rewriting anything in RBS. It reads source only — it does not load sorbet-runtime.

It ships bundled in rigortype. Activate it under plugins::

plugins:
  - rigor-sorbet

Full guide. This page is the operational quick reference. The complete walkthrough — the Sorbet→Rigor type-vocabulary table, every assertion form, RBI / Tapioca-DSL handling, sigil semantics, T.absurd exhaustiveness, and the migration patterns — is handbook chapter 10 — Coexisting with Sorbet.

Configuration

plugins:
  - gem: rigor-sorbet
    config:
      enforce_sigil: true              # default; honour `# typed:` sigils
      rbi_paths: ["sorbet/rbi"]        # default; set [] to disable RBI loading

• enforce_sigil (default true) — mirror Sorbet’s own contract: only record sigs from files at # typed: true or stricter. Set false to record sigs from every parseable file regardless of sigil. The inline assertion recognisers (T.let, T.cast, …) always fire, since the user wrote them deliberately.
• rbi_paths (default ["sorbet/rbi"]) — directories of .rbi files to load (the standard Tapioca subdirectories gems/ / annotations/ / dsl/ / shims/ participate by recursion). Set [] to opt out, or add a vendored tree.

Scope and limits

The plugin is input-side only: it translates Sorbet’s syntax into Rigor’s type model. It does not run Sorbet’s checker, ship sorbet-runtime, or enforce Sorbet’s runtime guarantees. When an RBS sig and a Sorbet sig disagree, RBS wins (the Sorbet sig may refine but not contradict it). Forms outside the translation table (T.proc, T.self_type, T::Struct / T::Enum subclasses, …) degrade to Dynamic[Top]. Chapter 10 documents the full vocabulary and these edges.

Plugin internals

The slice-by-slice implementation (sig parsing, assertion lifting, the RBI tree walker, mixin-chain resolution, the dispatcher tier ordering), the source layout, and the demo are in the plugin’s README. The design rationale is ADR-11.