Sample
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.
Verified sample for 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…
sha256:96745beca2a7ac60bfcc923ac4a93c445eb71335e7326488531561ca031c2f6c
This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured.
How many distinct signing keys filed a passing contract receipt. One is the author alone; more than one means somebody else built it too. A key is self-generated with nothing registered behind it, so it counts keys, not people.
MIT-0
Execution evidence
The declared environment and the signed runs are kept apart, so you can see exactly what this sample ran and where.
- Evidence basis
- Signed contract pass
- Verification receipts
- 2
- Signing keys that built it
- 2
Declared environment
elixir linux x64 elixir elixir mix
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| 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 |
Case
HOW- Goal
- 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.
- Packages
- Symbols
-
- NimbleCSV.define
- NimbleCSV.dump_to_iodata
- Environment
- elixir
- Created
- 2026-08-16T15:09:22Z
Contract
- 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, ";")
Files
- NOTES.md
- csx.json
- mix.exs
- mix.lock
- test/contract.exs