示例
nimble_csv 1.3.0: Show that when NimbleCSV.define/2 receives a list for :separator, the dumper is permanently fixed to the first entry at compile time — silently rewriting output that used any alternative separator during parsing.
已验证示例 — hex nimble_csv 1.3.0: Show that when NimbleCSV.define/2 receives a list for :separator, the dumper is permanently fixed to the first entry at compile…
sha256:96745beca2a7ac60bfcc923ac4a93c445eb71335e7326488531561ca031c2f6c
本网络只提供一件事：能构建的样本。它在沙箱中运行并保留签名回执。它不评级、不担保——同样的代码能否在你的环境构建，它没有测量过。
提交了通过的契约回执的不同签名密钥数量。为 1 表示只有作者；大于 1 表示还有其他人构建过。密钥是自行生成的，背后没有注册身份，因此计的是密钥而非人。
MIT-0
执行证据
声明的环境与签名的运行分开呈现，你可以看到这个样本究竟运行了什么、在哪里运行。
- 证据依据
- 签名契约通过
- 验证回执
- 2
- 构建过它的签名密钥
- 2
声明的环境
elixir linux x64 elixir elixir mix
验证运行环境
| 环境 | 契约 | 阶段 | 运行日期 |
|---|---|---|---|
| elixir 1 · linux alpine/x64 · docker ed25519:d91480838ac982c9 | PASS | compile:PASS · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · hex@1 |
2026-08-16 |
| elixir 1 · linux alpine/x64 · docker ed25519:2175b912ea1c23b1 | PASS | compile:PASS · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · hex@1 |
2026-08-18 |
案例
HOW- 目标
- Show that when NimbleCSV.define/2 receives a list for :separator, the dumper is permanently fixed to the first entry at compile time — silently rewriting output that used any alternative separator during parsing.
- 符号
-
- NimbleCSV.define
- NimbleCSV.dump_to_iodata
- 环境
- elixir
- 创建时间
- 2026-08-16T15:09:22Z
契约
- Parsing semicolon-separated CSV with a multi-separator parser succeeds, but dump_to_iodata emits pipe-separated output — the first separator in the list — not the semicolon the input used, because the dump separator is fixed at compile time by the first list entry.
- assert dumped == "alpha|beta\ngamma|delta\n"
- assert not String.contains?(dumped, ";")
文件
- NOTES.md
- csx.json
- mix.exs
- mix.lock
- test/contract.exs