namo 0.18.0 → 0.19.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 1ed38a77d14075cbe3c28ff53097d539c2fefe4a91ff515e165e02c280311fd3
-  data.tar.gz: ba009835a59174f2e60327f3583753d2e6c2b0e81b06f23de4a15dd792981526
+  metadata.gz: 35ca3cdc2c06b2da96ad636fa5ac1a593204a335ea93ff3994fc8bf187629aa5
+  data.tar.gz: 29639054075323f96fd0b6fe76bd733265ea155949965ec552c13ea30995efb8
 SHA512:
-  metadata.gz: 7328696a6b4032561fa1b68c0eb4d3e7d3582ee4d5fc24926779112413867f1713100d9c21a3aa2f18c299e50802c866b5c95e874e569f4ef41f40e7b3924f58
-  data.tar.gz: 8028776be37f1f183ca2cefc3c9de7229d6918cf37d05b5f925675dd2ffd7d05603cc21ba53665f74094991b0c8d08f22479de2f50ee35e36ba772777bdbfb6e
+  metadata.gz: 8e0be2ae49cd9cc493e580174b3edf8ac874592b45bd3de08ab1b5db3e7a83daa6d6f9c8efb97089b1653d61a92248a0ec7de60c7ab26beef98c0e9b3fab7a0f
+  data.tar.gz: 49a00bf247a8e286ee45e8619253d36ae8f77d2def369d377d5c46fa8c9ebad734513333d23472d9b8c074800f49a42292458505ad34281466079a73096e33aa

data/CHANGELOG

@@ -1,6 +1,23 @@
 CHANGELOG
 _________
 
+20260614
+0.19.0: ~ row-multiset equality — replace the sorted canonical form with a row multiset, so ==, eql?, hash, and the subset operators compare without sorting: nil/NaN-safe, row- and dimension-order blind, and consistently type-strict.
+
+1. ~ lib/namo.rb: replace canonical_data (which sorted @data by row.values_at(*data_dimensions.sort))
+   with row_multiset (@data.tally). ==, eql?, hash, and subset_of_rows? now compare row
+   multisets keyed by Hash#hash/#eql?. The sort was only ever a mechanism for reaching the
+   already-decided multiset semantics (0.6.0); a multiset reaches them directly and needs no
+   ordering, so the latent ArgumentError when a dimension mixed nil (or NaN) with present
+   values — neither has a <=> against the other — is gone. The relation is now uniformly
+   eql?-based, so == agrees with the subset operators, which already tallied: {a: 1} and
+   {a: 1.0} are consistently distinct (== previously called them equal via Hash#==, while <=
+   called them distinct).
+2. ~ test/namo_test.rb: + four "#==" cases — equality across row order and across dimension
+   (key) order when a dimension mixes nil and non-nil values; inequality when such rows
+   differ; and type-strictness on values, consistent with <=.
+3. ~ Namo::VERSION: /0.18.0/0.19.0/
+
 20260613
 0.18.0: + Namo::Collection — hierarchical aggregate of named Namos with summary/detail views.
 

data/README.md

@@ -1006,7 +1006,7 @@ gt.as_detail(:assembly)                    # gt's data becomes the detail; retur
 - If `by` is **already a dimension** in a member's rows, the row passes through untouched — the dimension is intrinsic.
 - If `by` is **not** present, `detail` injects it (`row.merge(by => member.name)`), promoting the member's name into a dimension.
 
-This single conditional is where assembly (`<<`, members named extrinsically) and partition (`group_by`, members named by an intrinsic value — 0.19.0) meet. For an assembled Collection, `as_detail(:assembly)` is the dimension-creating step: it promotes the member name into real data and **retains** it. From then on the structure is intrinsic and round-trips are exact; the promoted dimension is removed only by explicit contraction (`gt[-:assembly]`), never automatically.
+This single conditional is where assembly (`<<`, members named extrinsically) and partition (`group_by`, members named by an intrinsic value — 0.20.0) meet. For an assembled Collection, `as_detail(:assembly)` is the dimension-creating step: it promotes the member name into real data and **retains** it. From then on the structure is intrinsic and round-trips are exact; the promoted dimension is removed only by explicit contraction (`gt[-:assembly]`), never automatically.
 
 #### `<<` and unnamed members
 
@@ -1038,7 +1038,7 @@ gt << front_suspension                     # re-materialises detail
 gt.values(:weight)                         # => [200, 80, 150, 60, ...]   (line items again)
 ```
 
-Freeze-gated memoisation is a 2.x optimisation — opt-in via `freeze`, transparent, and never changing this observable behaviour. `group_by` (0.19.0) is the partition-side constructor for the same type: it splits a Namo into a `Collection`, the mirror of assembling one with `<<`.
+Freeze-gated memoisation is a 2.x optimisation — opt-in via `freeze`, transparent, and never changing this observable behaviour. `group_by` (0.20.0) is the partition-side constructor for the same type: it splits a Namo into a `Collection`, the mirror of assembling one with `<<`.
 
 ## Why?
 

data/lib/Namo/VERSION.rb

@@ -2,5 +2,5 @@
 # Namo::VERSION
 
 class Namo
-  VERSION = '0.18.0'
+  VERSION = '0.19.0'
 end

data/lib/namo.rb

@@ -164,7 +164,7 @@ class Namo
 
   def ==(other)
     return false unless other.is_a?(Namo)
-    canonical_data == other.canonical_data
+    row_multiset == other.row_multiset
   end
 
   def ===(other)
@@ -175,12 +175,12 @@ class Namo
 
   def eql?(other)
     self.class == other.class &&
-      canonical_data == other.canonical_data &&
+      row_multiset == other.row_multiset &&
       @formulae.keys.sort == other.formulae.keys.sort
   end
 
   def hash
-    [self.class, canonical_data, @formulae.keys.sort].hash
+    [self.class, row_multiset, @formulae.keys.sort].hash
   end
 
   def <(other)
@@ -217,13 +217,13 @@ class Namo
 
   protected
 
-  def canonical_data
-    @data.sort_by{|row| row.values_at(*data_dimensions.sort)}
+  def row_multiset
+    @data.tally
   end
 
   def subset_of_rows?(other)
-    self_counts = canonical_data.tally
-    other_counts = other.canonical_data.tally
+    self_counts = row_multiset
+    other_counts = other.row_multiset
     self_counts.all?{|row, count| (other_counts[row] || 0) >= count}
   end
 

data/test/namo_test.rb

@@ -2312,6 +2312,31 @@ describe Namo do
       _(a == 'string').must_equal false
       _(a == nil).must_equal false
     end
+
+    it "compares rows whose dimension mixes nil and non-nil values" do
+      a = Namo.new([{symbol: 'BHP', sector: 'Mining'}, {symbol: 'CBA', sector: nil}])
+      b = Namo.new([{symbol: 'CBA', sector: nil}, {symbol: 'BHP', sector: 'Mining'}])
+      _(a == b).must_equal true
+    end
+
+    it "is false for differing rows when a dimension contains nil" do
+      a = Namo.new([{symbol: 'BHP', sector: 'Mining'}, {symbol: 'CBA', sector: nil}])
+      b = Namo.new([{symbol: 'BHP', sector: 'Mining'}, {symbol: 'CBA', sector: 'Banking'}])
+      _(a == b).must_equal false
+    end
+
+    it "ignores dimension (key) order within a row" do
+      a = Namo.new([{a: 1, b: 2, c: 3}])
+      b = Namo.new([{c: 3, b: 2, a: 1}])
+      _(a == b).must_equal true
+    end
+
+    it "is type-strict on values, consistent with the subset operators" do
+      a = Namo.new([{x: 1}])
+      b = Namo.new([{x: 1.0}])
+      _(a == b).must_equal false
+      _(a <= b).must_equal false
+    end
   end
 
   describe "#===" do

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: namo
 version: !ruby/object:Gem::Version
-  version: 0.18.0
+  version: 0.19.0
 platform: ruby
 authors:
 - thoran