示例
Show that duplicate CSV headers are collapsed differently when a CSV row is converted through CSV::Row#to_h than by a generic Ruby Hash merge.
sha256:b4414ef0484dcdf82014555dba5031e1df164e93dc8a95ab9187db3918b6b2f0
PUBLISHED
L3_CONTRACT_PASS
MIT-0
案例
- 目标
- Show that duplicate CSV headers are collapsed differently when a CSV row is converted through CSV::Row#to_h than by a generic Ruby Hash merge. HOW
- 包
- csv 3.3.2
- 环境
- ruby
- 创建时间
- 2026-08-16T15:27:29Z
常见的想当然
A developer expects duplicated header values to follow normal Ruby Hash last-wins semantics when using CSV row conversion.
这是本样本作者记下的、开发者或模型在此处通常会有的预期。下面的契约才是真正运行过的东西。
契约
- CSV.parse("id,id,name\n1,2,alice\n", headers: true).first.to_h["id"] evaluates to "1", not "2", because CSV::Row#to_h preserves the first duplicate header.
- The same row converted with row.to_a.to_h returns "2" for key "id", showing that ordinary Ruby merge order rules do apply there.
文件
- Gemfile
- NOTES.md
- csx.json
- test/contract.rb
下载已验证的构件 (tar.gz) — 契约实际运行的那些字节
原始种子者
验证回执
- ruby 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · rubygems@1 · 2026-08-16 · ed25519:d91480838ac982c9