示例
Manage IO stream lifecycles, EOF positions, and monolithic buffer allocations in JSON.dump and JSON.load
sha256:ab7ff319b674d45bcbd2a67d43b257f7a387c8b14d38d85018607794429d5106
PUBLISHED
L3_CONTRACT_PASS
MIT-0
案例
- 目标
- Manage IO stream lifecycles, EOF positions, and monolithic buffer allocations in JSON.dump and JSON.load HOW
- 包
- json 2.9.1
- 环境
- ruby
- 创建时间
- 2026-08-17T02:43:58Z
常见的想当然
Passing an IO object to JSON.dump or JSON.load automatically closes or rewinds the stream upon completion, returns the serialized JSON string from dump, and streams writes and reads incrementally without buffering full documents in memory.
这是本样本作者记下的、开发者或模型在此处通常会有的预期。下面的契约才是真正运行过的东西。
契约
- assert JSON.dump and JSON.load leave passed IO streams open at EOF rather than closing or rewinding them, dump returns the IO object instead of the JSON string, and both operations buffer the entire payload in memory in a single monolithic read or write rather than streaming chunks
- assert JSON.dump and JSON.load leave the stream open and unrewound at EOF even when an error occurs during parsing or generation
- assert JSON.dump returns the IO instance when given a stream but returns a JSON String when the second argument is an integer limit
- assert JSON.parse rejects IO streams with TypeError, requiring explicit conversion to string or use of JSON.load with its unclosed stream caveat
- assert JSON::Parser retains its source string and re-parses from the retained string on subsequent parse calls rather than consuming or discarding it
- assert JSON.dump buffers the complete document before calling IO#write once, so a slow or aborted dump writes zero bytes rather than partial fragments
文件
- Gemfile
- Gemfile.lock
- NOTES.md
- csx.json
- src/resource_ops.rb
- test/contract.rb
下载已验证的构件 (tar.gz) — 契约实际运行的那些字节
原始种子者
验证回执
- ruby 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · rubygems@1 · 2026-08-17 · ed25519:d91480838ac982c9