rigortype 0.0.3 → 0.0.5

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 72dac247bb2b31d9f2b226d392242da9b6db2b3ee5638f4a6f66e8739019e18b
-  data.tar.gz: a39d687e673df117dc61182391a37a33b0a6c30e9489bd94549a7bf9ee8e5245
+  metadata.gz: 3b0e7446849097317ae0f4a26114036f41c4ad321abfcc492d25ac67995150b6
+  data.tar.gz: 95736bd636be7ba8698d4bf9a4cbdcbf870eaaf5a9117207f238f7429e064e94
 SHA512:
-  metadata.gz: 4aa2cfec0a5c4fd968fe0071d29073ab2131e802a1749f23009e5845d9efebff2e5abe58e97882911c34fb90c9ef32858a47acf7bc64d4b98b91bc7c5acf7bc6
-  data.tar.gz: 991d69e4ad0447c192c468ab13d387baee0334e401528b79676c9374b9b2137b6a3c4b3ada761e33e145ae963aee5fa6a8f7f84194a6c0b053bd1d4c39790507
+  metadata.gz: b16976fea05e9c4f9d9f9247e5858817e9938eff6329ce7e091f7c9196051170f3a36c528e6f6cb0386f4762c8b17302a6bb3a9df239e9385ec375a2c1b3a6ca
+  data.tar.gz: c8ac86259a502f4bfac5ef51464cf5eea45d599bdd3f9d164798b5b66a8257a8a117ea4e54b2314c27da9845a3723fa3fca61fe2f259988f2e19eb9b79c9df6d

data/README.md

@@ -1,152 +1,250 @@
 # Rigor
 
-Rigor is a static analyzer for Ruby that aims to provide modern,
-inference-first type checking without adding type annotations or
-runtime dependencies to application code.
-
-This first preview ships a usable end-to-end pipeline: parse Ruby
-with Prism, build a flow-sensitive type-inference engine
-(`Rigor::Scope#type_of`), drive a project-aware RBS environment,
-and surface diagnostics through a small `rigor check` rule
-catalogue.
-
-## Status
-
-The current branch (`impl/scope-type-of`) is a **first preview**.
-The engine recognises the bulk of canonical Ruby surface — local
-variables, ivars / cvars / globals (intra- and cross-method), self
-typing, lexical constant lookup, predicate narrowing
-(`is_a?` / `==` / `===` / `case`-`when`), block parameter binding,
-closure escape, Tuple / HashShape carriers, and more. See
-[docs/CURRENT_WORK.md](docs/CURRENT_WORK.md) for the full slice
-trail.
-
-## Requirements
-
-- Nix with the `nix-command` and `flakes` features available.
-- Ruby 4.0.x and Bundler 4.x, provided by the Flake development
-  shell.
+[![Gem Version](https://badge.fury.io/rb/rigortype.svg?icon=si%3Arubygems)](https://badge.fury.io/rb/rigortype)
+![GitHub License](https://img.shields.io/github/license/rigortype/rigor)
+
+**Inference-first static analysis for Ruby.** Add Rigor to your
+Gemfile and run `rigor check` over your code — no annotations,
+no runtime dependency on the analyzer, no DSL.
+
+Rigor parses Ruby with [Prism](https://github.com/ruby/prism),
+runs a flow-sensitive type-inference engine over each file,
+consults RBS signatures and the project's own `sig/` directory
+for any class it can find, and reports a small but trustworthy
+catalogue of bugs (undefined methods on typed receivers, wrong
+positional arity, provable `Integer / 0`, …).
+
+When you want tighter types than RBS expresses, refine them
+through the
+[`RBS::Extended`](docs/type-specification/rbs-extended.md)
+annotation surface — `rigor:v1:return:` /
+`rigor:v1:param:` / `rigor:v1:assert` directives accept the
+imported-built-in refinement names (`non-empty-string`,
+`positive-int`, `non-empty-array[Integer]`, `int<5, 10>`, …)
+without changing the underlying RBS.
+
+## Installation
+
+Add the gem to your application's Gemfile (development group is
+typical — Rigor is a static analyzer, not a runtime dependency):
+
+```ruby
+group :development do
+  gem "rigortype", require: false
+end
+```
 
-## Setup
+Install:
 
 ```sh
-nix --extra-experimental-features 'nix-command flakes' develop --command bundle install
-nix --extra-experimental-features 'nix-command flakes' develop --command bundle exec rake
+bundle install
 ```
 
-For interactive development, enter the Flake shell first:
+Or, for a one-off install outside Bundler:
 
 ```sh
-nix --extra-experimental-features 'nix-command flakes' develop
+gem install rigortype
 ```
 
-## Quick Start
+The gem ships an executable named `rigor` (gem name is
+`rigortype` because `rigor` was already taken on RubyGems).
 
-Inside the Flake shell:
+**Ruby version.** The gemspec requires `>= 4.0.0, < 4.1`.
 
-```sh
-# Show available subcommands.
-bundle exec exe/rigor help
+## First analysis
 
-# Print the inferred type at FILE:LINE:COL.
-bundle exec exe/rigor type-of lib/rigor/scope.rb:55:9
+Drop into your project root and run the canonical commands:
 
-# Report Scope#type_of coverage across a tree.
-bundle exec exe/rigor type-scan lib
+```sh
+# Diagnose unknown methods, wrong-arity calls, and other
+# rule-driven bugs across `lib/`.
+bundle exec rigor check lib
 
-# Diagnose unknown methods and wrong-arity calls on typed receivers.
-bundle exec exe/rigor check lib
+# Print the inferred type at a precise FILE:LINE:COL position.
+bundle exec rigor type-of lib/foo.rb:10:5
 
-# Write a starter .rigor.yml.
-bundle exec exe/rigor init
-```
+# Report Scope#type_of coverage across a tree (handy when
+# diagnosing why a particular call site reads as `untyped`).
+bundle exec rigor type-scan lib
 
-### Example diagnostics
+# Drop a starter .rigor.yml into the project root.
+bundle exec rigor init
+```
 
-`rigor check` reports the canonical type-check signals it can
-prove against the loaded RBS environment:
+### Sample output
 
 ```sh
 $ cat /tmp/demo.rb
-"hello".no_such_method        # bug: undefined method
-[1, 2, 3].rotate(1, 2)        # bug: wrong number of arguments
+"hello".no_such_method        # undefined method
+[1, 2, 3].rotate(1, 2)        # wrong number of arguments
 
-$ bundle exec exe/rigor check /tmp/demo.rb
+$ bundle exec rigor check /tmp/demo.rb
 /tmp/demo.rb:1:9: error: undefined method `no_such_method' for "hello"
 /tmp/demo.rb:2:11: error: wrong number of arguments to `rotate' on Array (given 2, expected 0..1)
 ```
 
-The rule catalogue is intentionally narrow: a diagnostic fires
-only when the receiver type is statically known and the method
-set on that class is enumerable through RBS or in-source `def` /
-`define_method` discovery. Implicit-self calls, dynamic
-receivers, and constant-decl alias classes (e.g. `YAML` → `Psych`)
-are skipped to avoid false positives.
-
-## What works
-
-The first preview engine resolves:
-
-- **Local / instance / class / global variables** — intra-method
-  bindings (`@x = 1; @x`), cross-method ivar / cvar accumulators
-  (`def init; @x = 1; end; def get; @x; end`), program-wide
-  globals.
-- **Compound writes** — `||=`, `&&=`, `+=` and friends thread
-  through scope for every variable kind.
-- **`self` typing** — class- and method-body boundaries inject
-  `Singleton[T]` / `Nominal[T]`; implicit-self call dispatch
-  routes through the enclosing class's RBS.
-- **Constant lookup** — lexical walk against `scope.self_type`,
-  RBS-core, common stdlib (`pathname`, `optparse`, `json`,
-  `yaml`, ...), the `prism` and `rbs` gems' RBS, in-source
-  class discovery, and in-source constant value tracking
-  (`BUCKETS = [:a, :b, :c]; BUCKETS.first` → `Constant[:a]`).
+The rule catalogue is **deliberately conservative**: a
+diagnostic fires only when the receiver type is statically
+known and the method set on that class is enumerable through
+RBS or in-source `def` / `define_method` discovery. Implicit-
+self calls, dynamic receivers, and constant-decl alias classes
+(e.g. `YAML` → `Psych`) are skipped to avoid false positives.
+
+## How Rigor finds your types
+
+Rigor consults, in order:
+
+1. **In-source RBS.** If your project has a `sig/` directory,
+   Rigor auto-loads it. `rigor init` writes a `.rigor.yml`
+   that points at `sig/` by default.
+2. **Bundled RBS core + stdlib.** Pathname, OptParse, JSON,
+   YAML, etc. ship with the analyzer.
+3. **Gem RBS.** RBS files vendored with installed gems
+   (Prism's own `.rbs`, the `rbs` gem's, …).
+4. **In-source class discovery.** When no RBS is available,
+   Rigor walks `def` / `define_method` / `attr_*` so
+   user-defined methods on a class are recognised.
+
+If a type cannot be proved, the engine returns `Dynamic[Top]`
+(Rigor's gradual carrier) and stays silent — Rigor never invents
+diagnostics it cannot prove.
+
+## Refining types through `RBS::Extended`
+
+When the RBS-declared type is too wide, attach a
+`%a{rigor:v1:…}` annotation to the relevant method in your
+`sig/` file. The annotation is a no-op for ordinary RBS tools
+and a tightening signal for Rigor.
+
+```rbs
+class Slug
+  # The runtime always returns a non-empty string. The override
+  # tightens the call-site result to non-empty-string and tells
+  # the body's `assert_type` that `id` cannot be "".
+  %a{rigor:v1:return: non-empty-string}
+  %a{rigor:v1:param: id is non-empty-string}
+  def normalise: (::String id) -> ::String
+end
+```
+
+Right-hand side accepts:
+
+- **RBS class names** — `String`, `::Foo::Bar` (with optional
+  `~T` negation for `assert` / `predicate-if-*`).
+- **Imported-built-in refinement names** (kebab-case):
+  - Point-removal — `non-empty-string`, `non-zero-int`,
+    `non-empty-array[T]`, `non-empty-hash[K, V]`.
+  - IntegerRange aliases — `positive-int`, `non-negative-int`,
+    `negative-int`, `non-positive-int`, `int<min, max>`.
+  - Predicate refinements — `lowercase-string`,
+    `uppercase-string`, `numeric-string`, `decimal-int-string`,
+    `octal-int-string`, `hex-int-string`.
+  - Composed shapes — `non-empty-lowercase-string`,
+    `non-empty-uppercase-string`.
+
+The full directive table is in
+[`docs/type-specification/rbs-extended.md`](docs/type-specification/rbs-extended.md);
+the catalogue of refinement names is in
+[`docs/type-specification/imported-built-in-types.md`](docs/type-specification/imported-built-in-types.md).
+
+### Example: argument-type-mismatch caught at the call site
+
+```rbs
+# sig/normaliser.rbs
+class Normaliser
+  %a{rigor:v1:param: id is non-empty-string}
+  def normalise: (::String id) -> ::String
+end
+```
+
+```ruby
+# app/normaliser.rb
+class Normaliser
+  def normalise(id)
+    id.upcase
+  end
+end
+
+n = Normaliser.new
+n.normalise("hello")   # OK
+n.normalise("")        # rigor flags: argument type mismatch
+```
+
+`rigor check` reports the second call as an
+`argument-type-mismatch` because the literal `""` does not
+satisfy `non-empty-string`. Inside the method body, Rigor also
+sees `id` as `non-empty-string` (so `id.empty?` reduces to
+`Constant[false]` and `id.size` reduces to `positive-int`).
+
+## What rigor sees today
+
+- **Local / instance / class / global variables** —
+  intra-method bindings, cross-method ivar / cvar
+  accumulators, program-wide globals, and compound writes
+  (`||=`, `&&=`, `+=`).
+- **`self` typing and constant lookup** — class and method
+  body boundaries inject `Singleton[T]` / `Nominal[T]`;
+  lexical constant resolution walks RBS-core, common stdlib,
+  in-source class discovery, and in-source constant-value
+  tracking (`BUCKETS = [:a, :b]; BUCKETS.first` →
+  `Constant[:a]`).
 - **Predicate narrowing** — truthiness, `nil?`, `is_a?` /
   `kind_of?` / `instance_of?`, finite-literal equality,
   case-equality (`===`) for Class / Module / Range / Regexp,
   `case` / `when` integration.
-- **Blocks** — parameter binding (incl. destructuring + numbered
-  parameters), block-return-type uplift through generic methods
-  (`Array#map { |n| n.to_s }` → `Array[String]`), closure escape
-  classification, captured-local invalidation on escaping blocks.
 - **Tuple / HashShape carriers** — shape-aware element access,
-  range / start-length slices, closed / open / required / optional
-  policies threaded through `Acceptance`.
-- **`rigor check` first-preview rules** — undefined method on
-  typed receiver, wrong number of positional arguments. Both
-  consult RBS plus in-source `def` / `define_method` discovery so
-  reopened classes do not produce false positives.
-
-See [docs/CURRENT_WORK.md](docs/CURRENT_WORK.md) for the canonical
-status snapshot, [docs/internal-spec/inference-engine.md](docs/internal-spec/inference-engine.md)
-for the engine contract, and [docs/adr/](docs/adr/) for the
-decision records.
-
-## Project layout
-
-- `lib/rigor` — runtime library, type model, inference engine, CLI.
-- `lib/rigor/analysis` — `Runner`, `CheckRules`, `Diagnostic`,
-  `FactStore`.
-- `lib/rigor/inference` — `Scope`-driven typers, dispatchers, and
-  narrowing.
-- `sig` — RBS signatures for Rigor itself.
-- `spec` — RSpec test suite (830+ examples).
-- `docs/adr` — architecture decision records.
-- `docs/internal-spec` — engine contracts.
-- `docs/type-specification` — type-language semantics.
-
-## Roadmap past first preview
-
-In rough priority order (see CURRENT_WORK.md for details):
-
-1. More `rigor check` rules (nil-call, type-incompatible writes,
-   unbound locals).
-2. `RBS::Extended` effect plumbing (`%a{rigor:v1:pure}`,
-   mutation / escape / call-timing effects).
-3. Diagnostic publication for `FallbackTracer` events.
-4. Plugin contribution layer.
+  range / start-length slices, closed / open / required /
+  optional policies.
+- **Constant folding** — aggressive arithmetic / string /
+  Symbol / Tuple-shaped `divmod` folding, cartesian fold over
+  `Union[Constant…]`, integer-range arithmetic
+  (`positive-int + 1` → `int<2, max>`), branch elision on
+  provably-truthy / falsey predicates.
+- **Built-in catalogues** — Numeric, String, Symbol, Array,
+  IO, File, Hash, Range, Set, Time. Each catalog drives the
+  fold dispatcher with per-class blocklists for indirect
+  mutators.
+- **Refinement carriers** — `Type::Difference`,
+  `Type::Refined`, `Type::Intersection` provide the
+  imported-built-in catalogue end-to-end through
+  `Builtins::ImportedRefinements`.
+- **`RBS::Extended` directive routes** — `return:`, `param:`
+  (call-site + body-side), `assert:` /
+  `predicate-if-(true|false)` accept refinement payloads.
+
+The full per-release surface lives in
+[`CHANGELOG.md`](CHANGELOG.md). The internal contracts the
+analyzer guarantees live under
+[`docs/internal-spec/`](docs/internal-spec/).
+
+## Configuration
+
+`rigor init` writes a starter `.rigor.yml`:
+
+```sh
+bundle exec rigor init           # fails if .rigor.yml exists
+bundle exec rigor init --force   # overwrite
+```
+
+The configuration is intentionally small in v0.0.x; see the
+generated file for the available knobs.
+
+## Status
+
+Current release: **`v0.0.4`** (the fourth preview). The
+analyzer is usable on real Ruby code today but the rule
+catalogue is deliberately narrow — Rigor's stance is to surface
+zero false positives while the inference surface stabilises.
+The roadmap is tracked in
+[`docs/MILESTONES.md`](docs/MILESTONES.md); release-by-release
+detail lives in [`CHANGELOG.md`](CHANGELOG.md).
+
+## Contributing
+
+See [`CONTRIBUTING.md`](CONTRIBUTING.md) for the minimal
+`git clone` → green-tests path and a map of the spec / ADR /
+skill documentation contributors should know about.
 
 ## License
 
-Rigor is licensed under the Mozilla Public License Version 2.0.
-See [LICENSE](LICENSE).
+Mozilla Public License Version 2.0. See [`LICENSE`](LICENSE).

data/data/builtins/ruby_core/comparable.yml

@@ -0,0 +1,87 @@
+# DO NOT EDIT — generated by tool/extract_builtin_catalog.rb
+---
+schema_version: 1
+generated_from:
+  ruby_init_c: references/ruby/compar.c
+  ruby_prelude:
+  rbs:
+  - references/rbs/core/comparable.rbs
+purity_levels:
+  leaf: Prelude :leaf marker (VM-enforced) or C body uses no dispatch/yield/mutation.
+  trivial: Prelude method body is a literal return (self/true/false/nil/Integer).
+  leaf_when_numeric: C body falls through to rb_num_coerce_* only when an operand
+    is non-numeric; safe to fold when every argument is a concrete numeric.
+  inline_block: Prelude method carries :inline_block or :use_block; block-dependent.
+  block_dependent: C body yields or checks rb_block_given_p.
+  mutates_self: C body checks rb_check_frozen — typically a prelude to mutation.
+  dispatch: C body calls user-redefinable methods (rb_funcall*, rb_equal, rb_Float,
+    num_funcall*, etc).
+  unknown: C body not located in indexed C files.
+classes:
+  Comparable:
+    parent: Module
+    defined_at: references/ruby/compar.c:324
+    includes: []
+    constants: {}
+    aliases: {}
+    instance_methods:
+      "==":
+        source: c
+        cfunc: cmp_equal
+        arity: 1
+        defined_at: references/ruby/compar.c:325
+        c_body_at: references/ruby/compar.c:79
+        c_effects:
+        - dispatch
+        purity: dispatch
+      ">":
+        source: c
+        cfunc: cmp_gt
+        arity: 1
+        defined_at: references/ruby/compar.c:326
+        c_body_at: references/ruby/compar.c:105
+        c_effects: []
+        purity: leaf
+      ">=":
+        source: c
+        cfunc: cmp_ge
+        arity: 1
+        defined_at: references/ruby/compar.c:327
+        c_body_at: references/ruby/compar.c:119
+        c_effects: []
+        purity: leaf
+      "<":
+        source: c
+        cfunc: cmp_lt
+        arity: 1
+        defined_at: references/ruby/compar.c:328
+        c_body_at: references/ruby/compar.c:137
+        c_effects: []
+        purity: leaf
+      "<=":
+        source: c
+        cfunc: cmp_le
+        arity: 1
+        defined_at: references/ruby/compar.c:329
+        c_body_at: references/ruby/compar.c:156
+        c_effects: []
+        purity: leaf
+      between?:
+        source: c
+        cfunc: cmp_between
+        arity: 2
+        defined_at: references/ruby/compar.c:330
+        c_body_at: references/ruby/compar.c:177
+        c_effects: []
+        purity: leaf
+      clamp:
+        source: c
+        cfunc: cmp_clamp
+        arity: -1
+        defined_at: references/ruby/compar.c:331
+        c_body_at: references/ruby/compar.c:231
+        c_effects:
+        - raises
+        purity: leaf
+    singleton_methods: {}
+    undefined: []