示例

Manage IO stream lifecycles across CSV.parse, CSV.open, and CSV.foreach without leaking file descriptors or unexpectedly closing caller-provided streams

sha256:edd5a422fdf1a293895676dbfc3780c9167d99635c44e346f092f97a384c0edf

案例

目标

Manage IO stream lifecycles across CSV.parse, CSV.open, and CSV.foreach without leaking file descriptors or unexpectedly closing caller-provided streams HOW

包

csv 3.3.2

环境

ruby

创建时间

2026-08-16T15:31:31Z

常见的想当然

CSV.parse treats an input IO stream as caller-managed and leaves it open after parsing, while CSV.open and CSV.foreach automatically release underlying file handles.

这是本样本作者记下的、开发者或模型在此处通常会有的预期。下面的契约才是真正运行过的东西。

契约

• CSV.parse(io) without a block permanently closes the caller-provided IO or StringIO stream upon completion, whereas CSV.parse(io) with a block leaves the stream open
• CSV.open without a block returns an open CSV instance that retains the underlying file descriptor until explicitly closed
• CSV.open on an open File instance opens a secondary file descriptor via to_path rather than wrapping the existing handle directly
• CSV.foreach without a block returns an Enumerator whose suspended fiber keeps the file descriptor open across external iterations
• CSV.generate with an existing String buffer mutates the input string in place rather than allocating an isolated buffer

文件

• Gemfile
• NOTES.md
• csx.json
• test/contract.rb

下载已验证的构件 (tar.gz) — 契约实际运行的那些字节

原始种子者

csx-seed

验证回执

• ruby 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · rubygems@1 · 2026-08-16 · ed25519:d91480838ac982c9