Issues

• Cross-impl: should error messages carry configuration values? (follow-up to ts.hocon#226)

  o3co/xx.hocon#119 · Filter by author y1o1 opened on Oct 16, 2026

• Cross-impl: self-reference inside a nested object of the same name — go errors, rs/ts/py and Lightbend disagree (fuzz seed 194)

  o3co/xx.hocon#116 · Filter by author y1o1 opened on Oct 15, 2026

• Cross-impl: an undefined ${?X} that replaces an object leaves the previous value in go/Lightbend, drops the key in rs/ts/py (fuzz seed 25)

  o3co/xx.hocon#115 · Filter by author y1o1 opened on Oct 15, 2026

• Cross-impl: integer literals beyond int64 — go alone rejects; Lightbend and ts/py/rs silently fall back to a double

  o3co/xx.hocon#99 · Filter by author y1o1 opened on Aug 26, 2026
  1

• P6: core include seam — include yaml(...) dispatch with per-parse format registration (design + cross-impl tracking)

  o3co/xx.hocon#98 · Filter by author y1o1 opened on Aug 20, 2026

• Cross-impl: key-position whitespace/adjacency accepted by Lightbend, rejected by all four siblings (#68 group B)

  o3co/xx.hocon#72 · Filter by author y1o1 opened on Jul 24, 2026

• Cross-impl: delayed-merge cycle-breaking lookback — all four siblings diverge from Lightbend (harvested object6)

  o3co/xx.hocon#67 · Filter by author y1o1 opened on Jul 24, 2026
  2