nosj 0.1.0-x86_64-linux → 0.3.0-x86_64-linux

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 0a0fd640bbecb91b12ed17a8ee5edc5b87befe85b1fcdcd124c58624255b3d02
-  data.tar.gz: 6cc111ee1c0a1d55640325d48e5b71fad155f18d218211a9fcaf2f3f2a3a54b7
+  metadata.gz: 734f363fe006f81b64302674599f01f78239515aba0111125b2db71a8ea70022
+  data.tar.gz: 2f13bcd853bd227de0420cc3c86c8452a2201705ea51192ac083c25fe0bf925b
 SHA512:
-  metadata.gz: 6dcc90744851a53f59a088e2ea4429ece7df99e2b72cbe81d049818641beb500b6847b9a3d9f703094c6d2f9aec669c89ab3ae652d47d29a8f3cefe0ee195ba9
-  data.tar.gz: 1f50198d497a46a8abbd281934ce3a04e5a704a1cbec221e2cf1dc0d570de817e447c4eb580c61e288960d5c797ba8f3f7b5e9215e85f90b439ae02e9dce57db
+  metadata.gz: 35091b15c193843620049fbc191beaad540c0774b3e6da311bf51dfdbf72f462e517ff3b527a474b0b62686d3ed4d828a4e610c9f5e6707055d19d61e7532327
+  data.tar.gz: 909edb0644da114fb00eba22c4c3d9a4d4e09a853b6f4652b28f62bb986f9342f5c7d91803126f213c3af8c4cc3070230f3bba222de1a7087cd47ccafa48d21b

data/CHANGELOG.md

@@ -1,4 +1,113 @@
-## [0.1.0] - 2026-07-15
+## [0.3.0] - 2026-07-17
+
+- Reformat without parsing. `NOSJ.minify(json, opts)` and
+  `NOSJ.reformat(json, opts)` (plus `NOSJ.reformat_file`) pipe the
+  parser's events straight into the emission kernels: zero Ruby
+  objects are allocated for the document, and output is exactly
+  `generate(parse(json))`—canonical numbers, normalized escapes, the
+  full set of `generate` formatting and escape options, with
+  `pretty: true` as a `pretty_generate` shorthand—except duplicate
+  object keys pass through and lone-surrogate string values re-escape
+  as `\uXXXX` instead of raising (the output must always reparse).
+  Acceptance options apply per `parse` (`allow_trailing_comma`
+  normalizes the commas away). Measured on the 631 KB twitter.json:
+  409µs, 3.4× faster than `NOSJ.generate(NOSJ.parse(x))`, 3.9× faster
+  than gem json's cycle, 5.3× faster than Oj's, and 1.4× the cost of
+  `NOSJ.valid?`.
+- Byte-splicing edits and JSON Patch. `NOSJ.splice(json, pointer =>
+  value, ...)` replaces values directly in the text: every target
+  resolves in one forward pass and the result is rebuilt copying all
+  bytes outside the target spans untouched (formatting, key order, and
+  number spellings elsewhere survive exactly). Measured on
+  twitter.json: 10× faster than parse-mutate-generate for a late
+  field, 51× for an early one. Missing targets raise KeyError,
+  overlapping targets ArgumentError. `NOSJ.patch(json, ops)` applies
+  RFC 6902 JSON Patch (add/remove/replace/move/copy/test, String or
+  Symbol op keys) to the raw string the same way, with structural ops
+  walking only the parent container's span; application failures raise
+  the new `NOSJ::PatchError`, malformed patch documents ArgumentError.
+  `NOSJ.merge_patch(json, patch)` applies RFC 7386 JSON Merge Patch
+  (semantic form). Inserted values are byte-identical to
+  `NOSJ.generate` and accept its options; the RFC 6902 appendix-A
+  suite and the full RFC 7386 test table are in the specs.
+- NDJSON / JSON Lines. `NOSJ.each_line(source, opts)` yields one
+  parsed value per line (Enumerator without a block, so
+  `.first(10)`/`.lazy` walk only what they consume), skipping blank
+  lines and enforcing one value per line; a malformed line raises the
+  rich `ParserError` whose `#line` is the physical line number in the
+  stream. `NOSJ.generate_lines(values, opts)` emits one compact
+  newline-terminated document per element in a single buffer pass
+  (measured 4.1× faster than the map-generate-join idiom on twitter
+  statuses; `each_line` is 1.6× faster than line-split +
+  `JSON.parse`), rejecting formatting options that would break line
+  framing. File forms: `NOSJ.each_line_file` streams over a read-only
+  memory map, `NOSJ.write_lines` generates straight to disk and
+  returns the byte count. Parse options apply per line; pass a frozen
+  string to `each_line` for zero-copy iteration.
+- `NOSJ.stats(source, opts)` / `NOSJ.stats_file(path, opts)`: document
+  statistics from one counting pass through the null-sink machinery,
+  answering "what is this 40 MB blob" without building any Ruby values
+  for the document (measured ~1.3× faster than a full parse). Reports
+  `byte_size`, `root` kind, `max_depth`, value counts by type, key
+  totals, a key histogram sorted by count, largest container sizes,
+  and string byte totals. Nesting is unlimited by default (pass
+  `max_nesting` to enforce a limit); `allow_nan` and
+  `allow_trailing_comma` are honored; malformed documents raise the
+  rich `ParserError`. The file form memory-maps, so the document never
+  enters Ruby at all.
+- Rich parse errors. Parse failures now raise `NOSJ::ParserError`
+  (previously a bare `RuntimeError`) carrying the failure position,
+  computed only when a parse fails: `#byte_offset`, 1-based `#line`,
+  character-based `#column`, and a caret `#snippet` showing the
+  offending line (windowed when the line is long, as minified JSON
+  usually is). Positions are absolute within the document you passed,
+  including through partial parsing (`dig`, `at_pointer`, batches),
+  lazy documents, and the file APIs. `#detailed_message` appends the
+  snippet, so unrescued errors print it. Failures with no position
+  (encoding refusals) leave the accessors nil. Exceeding `max_nesting`
+  during parsing now raises `NOSJ::NestingError`, matching the gem's
+  class (generation already did); rescues of the old `RuntimeError`
+  need updating to `NOSJ::ParserError`/`NOSJ::Error`.
+- Rails mode: `require "nosj/rails"` accelerates a Rails application
+  in both directions. It installs a nosj-backed ActiveSupport JSON
+  encoder, so `obj.to_json`, `render json:`, and `ActiveSupport::JSON.encode` walk the object tree natively—values recurse through `as_json` exactly
+  like ActiveSupport's own encoder. It also loads the `nosj/json` drop-in, so
+  `ActiveSupport::JSON.decode` and JSON request-body parsing take the
+  fast path (including on Rails 7.x, whose `quirks_mode` option the
+  drop-in now accepts; the drop-in also accepts valid-UTF-8 BINARY
+  strings now, which is what Rack delivers request bodies as). The
+  HTML-safety escaping is fused into the SIMD string-emission kernels,
+  so escaped output costs the same single pass as unescaped. Measured
+  against stock ActiveSupport encoding: ×1.7 on small documents up to
+  ×5.2 on large trees and ×14 on HTML-heavy content
+  (`rake bench:rails`). In a Rails Gemfile:
+  `gem "nosj", require: "nosj/rails"`.
+- `JSON::Fragment` values now splice their pre-rendered JSON
+  everywhere the `json` gem does: in default mode, under `strict:
+  true`, and through the Rails encoder.
+
+## [0.2.0] - 2026-07-16
+
+- File APIs. `NOSJ.load_file(path, opts)` parses a file directly
+  (~1.3× faster than `parse(File.read(path))`—no file-sized Ruby
+  String is created), and `NOSJ.write_file(path, obj, opts)` generates
+  straight to disk, returning the byte count like `File.write`.
+  `NOSJ.load_lazy_file(path, opts)` wraps a file as a lazy document
+  over a read-only memory map, and `NOSJ.at_pointer_file` /
+  `NOSJ.dig_file` pull single values out of a file without reading the
+  rest into Ruby. Missing files raise the usual `Errno` exceptions.
+- `NOSJ.lazy`: lazy documents. Wrap a document once, then read only
+  what you need: `doc["users"][3]["name"]` parses just that path, `#dig`
+  and `#at_pointer` resolve whole paths, and `#keys`, `#size`, and
+  `#each` inspect a node without parsing its values. Containers come
+  back lazy, scalars come back as plain Ruby values, and repeated
+  reads are cached. `#value` (also `#to_h` / `#to_a`) materializes a
+  subtree under the usual parse options (`symbolize_names`, `freeze`,
+  ...). Pass a frozen string and creating the view is practically
+  free, even on megabyte documents. Malformed content raises on first
+  read, not at wrap time.
+
+## [0.1.0] - 2026-07-16
 
 Initial release.
 

data/README.md

@@ -10,12 +10,17 @@
 - It is **faster** than gem json and every
 third-party parser, including Oj, RapidJSON, FastJsonparser, Yajl. 1.0–1.8× faster than the bundled json gem, 1.3–11× faster than Oj, and up to 17×
 faster than Yajl—[see Benchmarks](#benchmarks).
+- It has **lazy documents**: `NOSJ.lazy` wraps a document and parses a value only when you touch it—repeated access costs nanoseconds, and everything you never read is never parsed.
+- It has a **partial parsing mode**: JSON Pointer lookups that pull single values out of big documents in microseconds, skipping everything else.
+- It has **file APIs**: parse, generate, dig, and lazy-wrap files directly—no throwaway file-sized Ruby String, and the partial modes memory-map the file so unread pages never even leave the disk.
+- It does **byte-splicing edits**: `NOSJ.splice` changes a field inside a passing payload 10–51× faster than parse-mutate-generate, and RFC 6902 JSON Patch / RFC 7386 merge patch apply straight to the raw string.
+- It is **great to debug with**: parse errors carry line, column, and a caret snippet pointing at the break, and `NOSJ.stats` X-rays a mystery blob (depth, value counts, key histogram) faster than parsing it.
+- It accelerates a **Rails** application in both encoding and decoding.
 - It comes **precompiled** (platform gems built with per-platform optimizations,
 nothing to compile on install).
-- It has a **partial parsing mode**: JSON Pointer lookups that pull single values out of big documents in microseconds, skipping everything else.
-- Same API and option names as gem json.
+- Otherwise, same API and option names as gem json.
 
-**And there's more**: validate documents without building a single Ruby object, resolve whole batches of paths in one pass, and accelerate an entire application with a one-line drop-in.
+**And there's more**: validate documents without building a single Ruby object, minify and pretty-print without parsing, resolve whole batches of paths in one pass, stream NDJSON / JSON Lines in both directions, and accelerate an entire application with a one-line drop-in.
 
 - [Requirements](#requirements)
 - [Getting started](#getting-started)
@@ -24,6 +29,7 @@ nothing to compile on install).
 - [Switching from the json gem](#switching-from-the-json-gem)
 - [How it works](#how-it-works)
 - [Development](#development)
+- [Acknowledgements](#acknowledgements)
 - [License](#license)
 
 ## Requirements
@@ -48,6 +54,8 @@ NOSJ.generate({"a" => [1, true]})  #=> '{"a":[1,true]}'
 
 That's it—if you know the `json` gem, you already know `nosj`.
 
+### gem json compatibility
+
 Want the speedup without touching your code? One line reroutes
 `JSON.parse`, `JSON.generate`, `JSON.pretty_generate`, and `JSON.dump`
 through nosj:
@@ -63,18 +71,39 @@ Gemfile you can do this:
 gem "nosj", require: "nosj/json"
 ```
 
-Options nosj supports take the fast path; anything exotic
-(`create_additions`, `object_class`, `JSON::State`, procs, IO
-arguments) falls back to the original implementation, so `JSON.load`,
-`JSON.parse!`, and `JSON.load_file` keep their exact behavior.
-Exceptions re-raise as the JSON classes, so your rescue clauses keep
-working. Measured through the patch: parse 1.11×, generate 1.05× over
-the original gem. (A MultiJson adapter ships too:
-`require "nosj/multi_json"`, then `MultiJson.use NOSJ::MultiJsonAdapter`.)
+A MultiJson adapter ships too: 
+
+```ruby
+require "nosj/multi_json"
+```
+
+And then `MultiJson.use NOSJ::MultiJsonAdapter`.
+
+### Ruby on Rails
+
+In a Rails app, use this for "Rails mode":
+
+```ruby
+gem "nosj", require: "nosj/rails"
+```
+
+That installs a nosj-backed ActiveSupport JSON encoder, so `obj.to_json`, `render json:`, and `ActiveSupport::JSON.encode` walk the object tree natively:
+values that aren't JSON-native recurse through `as_json` exactly like
+ActiveSupport's own encoder, non-finite floats encode as `null`, and
+HTML-safety escaping (`escape_html_entities_in_json`) behaves
+identically—verified differentially against ActiveSupport's encoder.
+It loads the drop-in too, so `ActiveSupport::JSON.decode` and JSON
+request-body parsing ride the fast path. 
+
+Measured against ActiveSupport's own encoder: ×1.9 on small documents
+up to ×5.2 on large trees and ×14 on HTML-heavy content—see
+[Benchmarks → Rails mode](#rails-mode).
 
 ## What's in the box
 
-**The `json` gem API**, on the `NOSJ` module:
+### json API
+
+The `json` gem API, on the `NOSJ` module:
 
 ```ruby
 NOSJ.parse(src, symbolize_names: true)   # also: freeze, max_nesting,
@@ -83,18 +112,27 @@ NOSJ.generate(obj)                       # indent, space, object_nl, ...,
 NOSJ.pretty_generate(obj)                # ascii_only, script_safe, strict
 ```
 
-**Validation without parsing.** `NOSJ.valid?` runs the full
-parser—tokenizers, string decode, number validation—into a null sink
-and allocates no Ruby objects at all. It is 2-4× faster than
-`NOSJ.parse`, which already leads every parser above:
+### Lazy documents
+
+`NOSJ.lazy` wraps a document in a lazy view: read
+a field and only that path is parsed—containers stay lazy, scalars
+arrive as plain Ruby values, and repeated reads are cached:
 
 ```ruby
-NOSJ.valid?('{"a":1}')                #=> true
-NOSJ.valid?('{"a":}')                 #=> false
-NOSJ.valid?(src, max_nesting: false)  # same options as parse
+doc = NOSJ.lazy(json)
+doc["users"][3]["name"]   # parses only this path
+doc.dig("meta", "count")  # a whole path in one fused resolution
+doc["users"].size         # counted without materializing anything
+doc["users"][3].value     # materialize one subtree (parse options apply)
 ```
 
-**Partial parsing.** Pull values out of a document without
+Pass a frozen string and creating the view is practically free—
+nanoseconds, even on a megabyte document. Malformed content raises
+when it is first read, not at wrap time.
+
+### Partial parsing
+
+Pull values out of a document without
 materializing the rest—skipped content is stepped over at SIMD block
 speed, so a lookup costs what it skips, not what the document weighs:
 
@@ -114,11 +152,159 @@ at the far end of a 570 KB document costs ~71µs, still 13× faster
 than parse-then-dig. Misses return nil; matched subtrees materialize
 with the same options as `parse` (`symbolize_names:`, `freeze:`).
 
+### Files API
+
+Every mode has a file-native form, so a document never
+round-trips through a throwaway Ruby String:
+
+```ruby
+NOSJ.load_file("config.json")                 # 1.3× File.read + parse
+NOSJ.write_file("out.json", obj)              # generate straight to disk
+NOSJ.dig_file("huge.json", "users", 3, "name")   # never reads the rest
+NOSJ.at_pointer_file("huge.json", "/meta/count")
+doc = NOSJ.load_lazy_file("huge.json")        # lazy view over a memory map
+```
+
+The partial and lazy forms memory-map the file, so pages you never
+read are never loaded from disk. Missing files raise the usual
+`Errno` exceptions. Measured numbers live in
+[Benchmarks → File APIs](#file-apis).
+
+### Reformat without parsing
+
+`NOSJ.minify` and `NOSJ.reformat` pipe the parser's events straight
+into the emission kernels: **zero Ruby objects** are built for the
+document (the specs assert it), SIMD in and SIMD out. Minifying the
+631 KB twitter.json takes 409µs—3.4× faster than a
+`generate(parse(x))` round-trip, 3.9× faster than gem json's cycle,
+and only 1.4× the cost of `valid?`:
+
+```ruby
+NOSJ.minify(json)                        # compact
+NOSJ.reformat(json, pretty: true)        # pretty_generate layout
+NOSJ.reformat(json, ascii_only: true)    # escape-transcode, no parse
+NOSJ.reformat_file("big.json")           # straight off a memory map
+```
+
+Output is exactly `generate(parse(json))`—canonical number spellings,
+normalized escapes, same formatting options—except duplicate keys pass
+through (a reformatter must not silently drop data) and lone-surrogate
+strings re-escape instead of raising. Acceptance options apply too:
+`minify(src, allow_trailing_comma: true)` normalizes the commas away.
+
+### Byte-splicing edits and JSON Patch
+
+Change a field in a passing payload without the parse → mutate →
+generate cycle: `NOSJ.splice` skips to the target spans (one pass for
+the whole batch) and rebuilds the string around them—every byte
+outside the targets is copied untouched, so formatting, key order,
+and number spellings survive exactly. On twitter.json this is
+**10×–51× faster** than parse-mutate-generate (129µs for a late
+field, 26µs for an early one, vs ~1.3ms):
+
+```ruby
+NOSJ.splice(json, "/config/timeout" => 30)
+NOSJ.splice(json, "/a" => 1, "/b/c" => [true])   # batch, one pass
+```
+
+On top of the same machinery: **RFC 6902 JSON Patch** applied to the
+raw string (`add`, `remove`, `replace`, `move`, `copy`, `test`—the
+whole appendix-A suite is in the specs), and **RFC 7386 JSON Merge
+Patch**:
+
+```ruby
+NOSJ.patch(json, [
+  {"op" => "test", "path" => "/a", "value" => 1},
+  {"op" => "replace", "path" => "/a", "value" => 2},
+  {"op" => "add", "path" => "/list/-", "value" => "x"}
+])
+NOSJ.merge_patch(json, {"config" => {"legacy" => nil, "timeout" => 30}})
+```
+
+Missing splice targets raise `KeyError` (use `patch` `add` to
+insert); failed patches raise `NOSJ::PatchError`; inserted values are
+byte-identical to `NOSJ.generate`'s output.
+
+### NDJSON / JSON Lines
+
+Logs, data pipelines, LLM batch files—one JSON document per line.
+`NOSJ.each_line` streams values out (1.6× faster than the
+line-split-and-`JSON.parse` idiom on twitter statuses), and
+`NOSJ.generate_lines` builds the whole stream in one buffer pass
+(4.1× faster than map-generate-join):
+
+```ruby
+NOSJ.each_line(log) { |event| ingest(event) }   # or an Enumerator:
+NOSJ.each_line(log).first(10)                   # walks only 10 lines
+
+NOSJ.generate_lines(events)          #=> %({"a":1}\n{"b":2}\n...)
+NOSJ.each_line_file("events.ndjson") { |e| }    # over a memory map
+NOSJ.write_lines("out.ndjson", events)          # straight to disk
+```
+
+Blank lines are skipped, one value per line is enforced, and a
+malformed line raises a [rich `ParserError`](#rich-parse-errors) whose
+`#line` is the physical line in the stream. Parse options apply per
+line—`NOSJ.each_line(log, freeze: true)` yields Ractor-shareable
+values.
+
+### Validation without parsing
+
+`NOSJ.valid?` runs the full parser—tokenizers, string decode, 
+number validation—into a null sink and allocates no Ruby objects
+at all. It is 2-4× faster than `NOSJ.parse`:
+
+```ruby
+NOSJ.valid?('{"a":1}')                #=> true
+NOSJ.valid?('{"a":}')                 #=> false
+NOSJ.valid?(src, max_nesting: false)  # same options as parse
+```
+
+### Document statistics
+
+`NOSJ.stats` answers "what is this 40 MB blob": one counting pass 
+through the same null-sink machinery—no Ruby value is built for 
+the document, and it costs _less_ than a parse (~1.3× faster on `twitter.json`):
+
+```ruby
+s = NOSJ.stats(blob)          # or NOSJ.stats_file("huge.json")
+s[:byte_size]                 #=> 631514
+s[:root]                      #=> :object
+s[:max_depth]                 #=> 10
+s[:values]                    #=> {total: 13914, objects: 1264, arrays: 1050,
+                              #    strings: 4754, integers: 2108, ...}
+s[:keys]                      #=> {total: 13345, unique: 94}
+s[:key_histogram].first(3)    #=> [["id", 447], ["id_str", 447], ["urls", 364]]
+s[:containers]                #=> {max_object_entries: 40, max_array_length: 100}
+s[:strings]                   #=> {bytes: 200716, max_bytes: 463}
+```
+
+Nesting is unlimited by default (a deep blob is exactly what a
+diagnostic should describe); malformed documents raise the usual rich
+`ParserError`.
+
+### Rich parse errors
+
+A failed parse raises `NOSJ::ParserError`
+carrying where the document broke—`#byte_offset`, `#line`, `#column`,
+and a caret `#snippet`—computed only when a parse fails, so success
+pays nothing. Positions stay absolute through partial parsing, lazy
+documents, and the file APIs; unrescued errors print the snippet:
+
+```ruby
+NOSJ.parse(%({\n  "a": 1,\n  "b": }))
+# NOSJ::ParserError: unexpected character at byte 19
+#   e.line     #=> 3
+#   e.column   #=> 8
+#   e.snippet  #=>   "b": }
+#                         ^
+```
+
 ## Benchmarks
 
 Every installed JSON gem, benchmark-ips: AWS EC2 c7a.2xlarge (AMD EPYC 9R14, Zen 4), Ruby 4.0.6 + YJIT, json 2.21.1, Oj 3.17.4, RapidJSON 0.4.0, FastJsonparser 0.6.0, Yajl 1.4.3, PGO build, 2026-07-16. `×N` = times slower than nosj. 
 
-Parse:
+### Parse
 
 | file | nosj (i/s) | json | Oj | FastJsonparser | RapidJSON | Yajl |
 |---|---:|---:|---:|---:|---:|---:|
@@ -136,7 +322,7 @@ Parse:
 | tolstoy | **8.9k** | ×1.79 | ×1.96 | ×2.29 | ×2.10 | ×17.31 |
 | twitter | **1.1k** | ×1.09 | ×1.83 | ×2.25 | ×2.61 | ×5.40 |
 
-Generate:
+### Generate
 
 | file | nosj (i/s) | json | Oj | RapidJSON | Yajl |
 |---|---:|---:|---:|---:|---:|
@@ -157,6 +343,44 @@ Generate:
 \* canada-generate is a statistical tie with the json gem (within
 measurement error).
 
+### File APIs
+
+twitter.json (570 KB) from a warm page cache, medians of 7 alternating
+rounds against the plain-Ruby composition on the same parser (Apple
+Silicon dev box, Ruby 4.0.6 + YJIT, PGO build, 2026-07-16):
+
+| operation | µs/op | vs the Ruby way |
+|---|---:|---|
+| `NOSJ.load_file` (parse the whole file) | 948 | ×1.33 vs `NOSJ.parse(File.read(path))` |
+| `NOSJ.dig_file` (one deep field) | 246 | ×5.2 vs read + parse + dig |
+| `NOSJ.load_lazy_file` + one field | 257 | ×5.0 vs read + parse + dig |
+
+`NOSJ.write_file` measures at parity with
+`File.write(NOSJ.generate(obj))` on this box—file-write timings swing
+too much for an honest multiplier; what it saves is the intermediate
+file-sized Ruby String.
+
+### Rails mode
+
+`ActiveSupport::JSON.encode` with the nosj encoder installed, against
+stock ActiveSupport (Apple Silicon dev box, Ruby 4.0.6 + YJIT,
+activesupport 8.1, medians of 5 interleaved per-process rounds,
+outputs verified byte-identical first, 2026-07-17;
+`rake bench:rails`):
+
+| workload | nosj (i/s) | vs ActiveSupport |
+|---|---:|---|
+| twitter tree (570 KB) | 4.5k | ×5.2 |
+| 100-record index (with timestamps) | 33.7k | ×1.7 |
+| HTML-heavy user content | 177.7k | ×14.2 |
+| Time/Date/BigDecimal hash | 1.1M | ×3.0 |
+| small API hash | 4.2M | ×1.9 |
+| small hash `to_json` | 4.1M | ×1.9 |
+
+The HTML-safety escaping that dominates stock encodes of
+user-generated content is fused into the SIMD string-emission kernels
+here: escaped output costs the same single pass as unescaped.
+
 Reproduce with `rake bench` (the parity-gated comparison, after a PGO retrain—the shipping configuration) or `rake bench:ips` (the multi-gem shoot-out).
 
 ## Switching from the json gem
@@ -170,8 +394,10 @@ You mostly don't have to do anything. Some differences:
   UTF-8) follow the strict semantics instead.
 - Unlike `Array#dig`, negative indices in `NOSJ.dig` return nil (JSON
   Pointer has no equivalent).
-- Parse error *messages* use byte offsets rather than the gem's
-  phrasing (classes match).
+- Parse errors raise `NOSJ::ParserError` (`NOSJ::NestingError` past
+  `max_nesting`, like the gem); messages use byte offsets rather than
+  the gem's phrasing, and the exception carries `#line`, `#column`,
+  and a caret `#snippet`.
 
 Everything else—including the gem's exact float formatting, which is
 not the shortest-round-trip form most libraries emit—matches
@@ -208,6 +434,28 @@ bundle exec rake bench:fast             # the sweep without retraining
 bundle exec rake "bench:ips[twitter]"   # multi-gem shoot-out (benchmark-ips); no args = full corpus
 ```
 
+## Acknowledgements
+
+Thanks to [Jean Boussier](https://github.com/byroot), [Florian Frank](https://github.com/flori), [Hiroshi Shibata](https://github.com/hsbt), [Nobuyoshi Nakada](https://github.com/nobu), [Étienne Barrié](https://github.com/etiennebarrie), and the other authors and maintainers of the [json gem](https://github.com/ruby/json)—for their work on the gem itself, for optimization ideas, and for some of the JSON documents in the benchmark corpus.
+
+Thanks to [Mat Sadler](https://github.com/matsadler) for [magnus](https://github.com/matsadler/magnus).
+
+Thanks to the authors of the projects credited in [NOTICE](NOTICE) and the
+crate's NOTICE: [fpconv](https://github.com/night-shift/fpconv) and
+Florian Loitsch's Grisu2,
+[fast_float](https://github.com/fastfloat/fast_float) and
+[fast_double_parser](https://github.com/lemire/fast_double_parser)
+(Daniel Lemire et al.),
+[simdjson](https://github.com/simdjson/simdjson) (Daniel Lemire, Geoff
+Langdale, and contributors), and the architectural lineage of
+[yyjson](https://github.com/ibireme/yyjson),
+[simd-json](https://github.com/simd-lite/simd-json), and
+[sonic-rs](https://github.com/cloudwego/sonic-rs).
+
+## Assisted by
+
+Claude Fable 5, Claude Opus 4.8.
+
 ## License
 
 MIT. The underlying Rust crate is `MIT AND BSL-1.0 AND Apache-2.0`; its

data/lib/nosj/json.rb

@@ -6,7 +6,7 @@
 #
 # reroutes JSON.parse, JSON.generate, JSON.pretty_generate and JSON.dump
 # through NOSJ whenever the requested options fall within NOSJ's
-# supported set, and falls back to the original json implementation for
+# supported set, and falls back to gem json's own implementation for
 # everything else (create_additions, object_class/array_class,
 # decimal_class, on_load procs, JSON::State instances, IO arguments).
 # Entry points built on JSON.parse (JSON.load, JSON.parse!,
@@ -30,8 +30,11 @@ module NOSJ
   # Implementation detail of `require "nosj/json"`.
   # @private
   module JSONDropIn
+    # quirks_mode rides the fast path because NOSJ.parse is always
+    # quirks-mode (top-level scalars parse) and ignores the key; Rails
+    # 7.x passes it from ActiveSupport::JSON.decode.
     PARSE_OPTS = %i[symbolize_names freeze max_nesting allow_nan
-      allow_trailing_comma].freeze
+      allow_trailing_comma quirks_mode].freeze
     GENERATE_OPTS = %i[indent space space_before object_nl array_nl
       max_nesting allow_nan ascii_only script_safe
       escape_slash strict depth
@@ -41,7 +44,7 @@ module NOSJ
 
     # The fast path handles nil or a plain Hash whose every key NOSJ
     # implements; anything else (JSON::State, exotic options, string
-    # keys) belongs to the original implementation.
+    # keys) belongs to gem json.
     def supported?(opts, allowed)
       return true if opts.nil?
       return false unless opts.instance_of?(Hash)
@@ -50,8 +53,29 @@ module NOSJ
     end
 
     def parse(source, opts)
+      # NOSJ.parse is deliberately strict about encodings (json-3.0
+      # semantics), but the drop-in must match the installed gem, which
+      # accepts more. BINARY strings holding valid UTF-8 are the big
+      # real-world case: Rack delivers request bodies as BINARY, so
+      # Rails JSON params come through here. Retagging a dup is cheap
+      # (copy-on-write bytes), and the validity scan is memoized
+      # coderange the parse would compute anyway. Anything else
+      # non-UTF-8 (UTF-16, ...) belongs to gem json, which transcodes.
+      if source.is_a?(String)
+        case source.encoding
+        when Encoding::UTF_8, Encoding::US_ASCII
+        # the fast path as-is
+        when Encoding::BINARY
+          utf8 = source.dup.force_encoding(Encoding::UTF_8)
+          source = utf8 if utf8.valid_encoding?
+        else
+          return ::JSON.nosj_original_parse(source, **(opts || {}))
+        end
+      end
       NOSJ.parse(source, opts)
-    rescue RuntimeError => e
+    rescue NOSJ::NestingError => e
+      raise ::JSON::NestingError, e.message
+    rescue NOSJ::ParserError => e
       raise ::JSON::ParserError, e.message
     end
 
@@ -103,9 +127,9 @@ module JSON
 
       def dump(obj, an_io = nil, limit = nil, kwargs = nil)
         # Fast path for the common shapes, dump(obj) and dump(obj, opts
-        # hash), mirroring the gem: dump defaults merged under the
+        # hash), mirroring gem json: dump defaults merged under the
         # user's options, NestingError surfaced as ArgumentError. IO and
-        # limit arguments take the original implementation.
+        # limit arguments take gem json's own dump.
         if limit.nil? && kwargs.nil? && (an_io.nil? || an_io.instance_of?(Hash))
           opts = _dump_default_options
           opts = opts.merge(an_io) if an_io