rigortype 0.4.3 → 0.4.4

data/plugins/rigor-rspec/lib/rigor/plugin/rspec.rb

@@ -86,7 +86,7 @@ module Rigor
       # ADR-37 slice 2 — matcher narrowing (`expect(x).to be_a(T)` → `post_return_facts` on `x`),
       # method-gated by the engine on the expectation verbs.
       narrowing_facts methods: %i[to not_to to_not] do |call_node, scope|
-        MatcherAnalyzer.contribution_for(call_node, environment: scope&.environment)&.post_return_facts
+        MatcherAnalyzer.contribution_for(call_node, scope: scope)&.post_return_facts
       end
 
       # ADR-52 slice 5a — binds local reads in `it` / spec bodies to their `let(:name) { ... }` block's
@@ -98,13 +98,15 @@ module Rigor
         let_binding_return_type(call_node, scope)
       end
 
-      # ADR-88 WD1 — both contributions are per-file: the matcher narrowing facts come from the call's own AST,
-      # and the `let`-binding return types come from each spec file's OWN `describe`/`let` structure (`let` is
-      # file-scoped). A spec file's edit changes its own content (re-analysed already). The one cross-file input
-      # — the optional factorybot `:factory_index` fact this plugin consumes — is itself an ADR-9 publication
-      # captured in the incremental fact-surface digest via factorybot's own channel, so it need not appear
-      # here. A stable sentinel declares "no OWN cross-file fact surface", keeping the plugin
-      # incremental-capable; `--verify-incremental` backstops the claim.
+      # ADR-88 WD1 — both contributions are per-file: the matcher narrowing facts come from the call's own AST
+      # and, for `eq` / `eql`, from the local's current type and the scope's project discovery (whether the
+      # project defines `==` / `eql?` on a core class); the `let`-binding return types come from each spec
+      # file's OWN `describe`/`let` structure (`let` is file-scoped). A spec file's edit changes its own
+      # content (re-analysed already). The one cross-file input — the optional factorybot `:factory_index`
+      # fact this plugin consumes — is itself an ADR-9 publication captured in the incremental fact-surface
+      # digest via factorybot's own channel, so it need not appear here. A stable sentinel declares "no OWN
+      # cross-file fact surface", keeping the plugin incremental-capable; `--verify-incremental` backstops
+      # the claim.
       def incremental_state_fingerprint
         "per-file-lets"
       end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: rigortype
 version: !ruby/object:Gem::Version
-  version: 0.4.3
+  version: 0.4.4
 platform: ruby
 authors:
 - Rigor contributors
@@ -321,6 +321,7 @@ files:
 - data/core_overlay/module.rbs
 - data/core_overlay/numeric.rbs
 - data/core_overlay/object_space.rbs
+- data/core_overlay/ostruct.rbs
 - data/core_overlay/pathname.rbs
 - data/core_overlay/proc.rbs
 - data/core_overlay/process.rbs
@@ -830,6 +831,7 @@ files:
 - lib/rigor/inference/refined_dispatch/class_object.rb
 - lib/rigor/inference/refined_dispatch/own_method.rb
 - lib/rigor/inference/refinement_mutation.rb
+- lib/rigor/inference/reflective_ivar_write.rb
 - lib/rigor/inference/repeated_or_writes.rb
 - lib/rigor/inference/return_barrier.rb
 - lib/rigor/inference/rewrite_mutation.rb
@@ -841,6 +843,7 @@ files:
 - lib/rigor/inference/scope_indexer/member_layouts_collector.rb
 - lib/rigor/inference/scope_indexer/mixin_accumulator.rb
 - lib/rigor/inference/scope_indexer/superclasses_collector.rb
+- lib/rigor/inference/self_call_ivar_writes.rb
 - lib/rigor/inference/singleton_hook_decline.rb
 - lib/rigor/inference/singleton_object_constant.rb
 - lib/rigor/inference/statement_evaluator.rb